PHOENIX CONTACT: Improper path sanitation on import of project files in PLCnext Engineer
The build settings of a PLCnext Engineer project (.pcwex) can be manipulated in a way that can result in the execution of remote code. The attacker needs to get access to a PLCnext Engineer project to be able to manipulate files inside. Additionally, the files of the remote code need to be transferred to a location which can be accessed by the PC that runs PLCnext Engineer. When PLCnext Engineer runs a build process of the manipulated project the remote code can be executed.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-12499US | high7.3 | — | ||
In PHOENIX CONTACT PLCnext Engineer version 2020.3.1 and earlier an improper path sanitation vulnerability exists on import of project files. | ||||
references
External citations — patches, advisories, analysis.
- VDE-2020-025: PHOENIX CONTACT: Improper path sanitation on import of project files in PLCnext Engineer - HTMLself
- CERT@VDE Security Advisories for Phoenix Contact GmbH & Co. KGexternal
- VDE-2020-025: PHOENIX CONTACT: Improper path sanitation on import of project files in PLCnext Engineer - CSAFself
- Phoenix Contact PSIRTexternal
remediations (2)
- MitigationPLCnext Engineer
We strongly recommend customers to exchange project files only using secure file exchange services. Project files should not be exchanged via unencrypted email. Users should avoid importing project files from unknown source and exchange or store project files together with a checksum to ensure their integrity.
- FixedPLCnext Engineer
Phoenix Contact strongly recommends updating to the latest version PLCnext Enineer 2020.6, which fixes this vulnerability.
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan