Remote PLC logic execution via collision-prone CRCs
Published Dec 14, 2023 · Updated Aug 2, 2024
Code integrity failure in all versions of Phoenix Contact MULTIPROG and ProConOS eCLR allows remote attackers to execute altered PLC applications. The engineering integrity comparison trusts a project header stamp and two collision-prone CRC values, so out-of-band logic changes can retain values that appear valid. No authentication or user interaction is required; successful manipulation can replace application logic while the workstation reports no difference.
Summary
What happened
Code integrity failure in all versions of Phoenix Contact MULTIPROG and ProConOS eCLR allows remote attackers to execute altered PLC applications. The engineering integrity comparison trusts a project header stamp and two collision-prone CRC values, so out-of-band logic changes can retain values that appear valid. No authentication or user interaction is required; successful manipulation can replace application logic while the workstation reports no difference.
The record
- CVE
- CVE-2023-5592
- Published
- Dec 14, 2023
- Updated
- Aug 2, 2024
- Vendor
- Phoenix Contact
- Product
- MULTIPROG
- Classifications
- CWE-494, T0843
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=all
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo