Process crash via out-of-bounds message read
Published Jul 15, 2022 · Updated Aug 3, 2024
A stack-buffer overflow in EIPStackGroup OpENer 2.3.0 allows attackers to crash the process with a crafted incoming message. The POSIX executable reads one byte beyond the 512-byte incoming_message stack buffer, and AddressSanitizer aborts at frame offset 560. Triggering the demonstrated condition requires a valid EtherNet/IP session and the project's testcase sender; public evidence demonstrates a crash, not code execution.
Summary
What happened
A stack-buffer overflow in EIPStackGroup OpENer 2.3.0 allows attackers to crash the process with a crafted incoming message. The POSIX executable reads one byte beyond the 512-byte incoming_message stack buffer, and AddressSanitizer aborts at frame offset 560. Triggering the demonstrated condition requires a valid EtherNet/IP session and the project's testcase sender; public evidence demonstrates a crash, not code execution.
The record
- CVE
- CVE-2022-32434
- Published
- Jul 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T0814
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- OpENer issue 374 poc.zip and send_testcase.pyproof of concept · demonstrated
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