Utility crash via le_uint32_read heap overflow
Published Aug 29, 2022 · Updated Aug 3, 2024
Heap buffer overflow in AdvanceCOMP 2.3 allows local users to crash a utility by processing a crafted input file. The le_uint32_read routine in lib/endianrw.h reads a 32-bit little-endian value beyond the heap buffer boundary while parsing malformed input. Processing attacker-supplied input is required, and the documented consequence is a crash rather than data disclosure or modification.
Summary
What happened
Heap buffer overflow in AdvanceCOMP 2.3 allows local users to crash a utility by processing a crafted input file. The le_uint32_read routine in lib/endianrw.h reads a 32-bit little-endian value beyond the heap buffer boundary while parsing malformed input. Processing attacker-supplied input is required, and the documented consequence is a crash rather than data disclosure or modification.
The record
- CVE
- CVE-2022-35015
- Published
- Aug 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 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.
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
- CVE-2022-35015 crashing-input proof of conceptproof of concept · unverified
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