When CX-Supervisor (Versions 3.42 and prior) processes project files and tampers with the value of an offset, an attacker can force the application to read a value outside of an array.
Product
ICS-CERT CX-Supervisor vulnerabilities
7 published CVES affecting ICS-CERT CX-Supervisor, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 7
- Critical
- 0
- High
- 5
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest ICS-CERT CX-Supervisor CVEs
Newest publication first
-
MediumCVSS 5.0 EPSS 0.83%
-
HighCVSS 7.3 EPSS 1.2%
An access of uninitialized pointer vulnerability in CX-Supervisor (Versions 3.42 and prior) could lead to type confusion when processing project files. An attacker could use a specially crafted project file to exploit and execute code under the privileges of the application.
-
HighCVSS 7.3 EPSS 1.5%
An attacker could inject commands to launch programs and create, write, and read files on CX-Supervisor (Versions 3.42 and prior) through a specially crafted project file. An attacker could exploit this to execute code under the privileges of the application.
-
HighCVSS 7.3 EPSS 1.5%
A type confusion vulnerability exists when processing project files in CX-Supervisor (Versions 3.42 and prior). An attacker could use a specially crafted project file to exploit and execute code under the privileges of the application.
-
HighCVSS 8.8 EPSS 2.4%
Several use after free vulnerabilities have been identified in CX-Supervisor (Versions 3.42 and prior). When processing project files, the application fails to check if it is referencing freed memory. An attacker could use a specially crafted project file to exploit and execute c...
-
MediumCVSS 5.0 EPSS 0.75%
An attacker could inject commands to delete files and/or delete the contents of a file on CX-Supervisor (Versions 3.42 and prior) through a specially crafted project file.
-
HighCVSS 8.8 EPSS 2.4%
CX-Supervisor (Versions 3.42 and prior) can execute code that has been injected into a project file. An attacker could exploit this to execute code under the privileges of the application.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.