Phoenix Contact has a series of recommendations to handle stack-based buffer overflow and out-of-bounds read vulnerabilities in its Automation Worx Software Suite, according to a report with CISA.
Successful exploitation of the vulnerabilities, discovered by Natnael Samson and mdm, working with Trend Micro Zero Day Initiative, could allow an attacker to execute arbitrary code under the privileges of the application.
The following components and versions of Automation Worx Software Suite suffer from the issues:
- PC Worx version 1.87 and prior
- PC Worx Express version 1.87 and prior
In one vulnerability, due to insufficient input data validation while processing project files an attacker could overflow the buffer. An attacker could use a specially crafted project file to exploit and execute code under the privileges of the application.
CVE-2020-12497 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.8.
In addition, there is insufficient input data validation while processing project files which could result in an out-of-bounds read. An attacker could use a specially crafted project file to exploit and execute code under the privileges of the application.
CVE-2020-12498 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.8.
The product sees use in the communications, critical manufacturing, and information technology sectors. It also sees action on a global basis.
No known public exploits specifically target these vulnerabilities. These vulnerabilities are not remotely exploitable. However, an attacker with low skill level could leverage the vulnerabilities.
In terms of mitigating the issue, Phoenix Contact recommends users exchange project files only using secure file exchange services. Users should not exchange project files via unencrypted email. In addition, by exchanging or storing project files together with a checksum would ensure their integrity.
With the next version of Automation Worx Software Suite, a sharpened input data validation, with respect to buffer size and description of size and number of objects referenced in a file, will end up implemented.

