Malicious logic execution via bypassed integrity checks
Published Dec 14, 2023 · Updated Aug 2, 2024
Incorrect permission assignment in Phoenix Contact PLCnext products through 2024.0 allows remote authenticated users to upload malicious logic. The application integrity check accepts specially crafted logic files, executable logic, or configurations without recognizing their tampering. Exploitation requires authenticated network or physical access to an engineering station, stored application, transfer path, or controller, and grants control of PLC logic and runtime data.
Summary
What happened
Incorrect permission assignment in Phoenix Contact PLCnext products through 2024.0 allows remote authenticated users to upload malicious logic. The application integrity check accepts specially crafted logic files, executable logic, or configurations without recognizing their tampering. Exploitation requires authenticated network or physical access to an engineering station, stored application, transfer path, or controller, and grants control of PLC logic and runtime data.
The record
- CVE
- CVE-2023-46142
- Published
- Dec 14, 2023
- Updated
- Aug 2, 2024
- Vendor
- Phoenix Contact
- Product
- BPC 9102S
- Classifications
- CWE-732, T0843
- Attack vector
- network
- Privileges
- authenticated
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=0 <=2024.0
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.
Weakness, pattern, technique
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