Runtime crash via undersized OPC UA receive buffer
Published Jun 4, 2024 · Updated Aug 1, 2024
Buffer-size miscalculation in affected CODESYS products allows remote attackers to crash the runtime through crafted OPC UA traffic. CmpOPCUAStack miscalculates the required buffer size for a received request or response, then crashes while zero-initializing the receive buffer. An unauthenticated malicious client can target an OPC UA server; an OPC UA client also crashes after connecting to a malicious server.
Summary
What happened
Buffer-size miscalculation in affected CODESYS products allows remote attackers to crash the runtime through crafted OPC UA traffic. CmpOPCUAStack miscalculates the required buffer size for a received request or response, then crashes while zero-initializing the receive buffer. An unauthenticated malicious client can target an OPC UA server; an OPC UA client also crashes after connecting to a malicious server.
The record
- CVE
- CVE-2024-5000
- Published
- Jun 4, 2024
- Updated
- Aug 1, 2024
- Vendor
- CODESYS GmbH
- Product
- CODESYS Control for BeagleBone SL
- Classifications
- CWE-131, CAPEC-100, CAPEC-47, T1499.004, T0814
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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 <4.12.0.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