Code execution via corrupt project file parsing
Published May 6, 2024 · Updated Aug 2, 2024
Out-of-bounds write in CODESYS Development System V2.3 before 2.3.9.73 allows local users to execute code via a corrupt project file. The project loader continues processing a file identified as corrupt after warning confirmation, allowing malformed content to write beyond a memory buffer. Exploitation requires a user to accept the warning and open the attacker-supplied file; successful exploitation runs code in the application context or crashes it.
Summary
What happened
Out-of-bounds write in CODESYS Development System V2.3 before 2.3.9.73 allows local users to execute code via a corrupt project file. The project loader continues processing a file identified as corrupt after warning confirmation, allowing malformed content to write beyond a memory buffer. Exploitation requires a user to accept the warning and open the attacker-supplied file; successful exploitation runs code in the application context or crashes it.
The record
- CVE
- CVE-2023-49675
- Published
- May 6, 2024
- Updated
- Aug 2, 2024
- Vendor
- CODESYS GmbH
- Product
- CODESYS Development System
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2024CVE 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 <2.3.9.73
- Affected versionversion=2.3
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