Process abort via uncaught allocation exception
Published Mar 27, 2024 · Updated Aug 20, 2024
Resource exhaustion in Precomp 0.4.8 allows local users to abort the process by processing a specially crafted input file. A supplied file processed in recursive mode triggers an allocation failure, and the resulting std::bad_alloc exception escapes handling and terminates the process. The demonstrated impact is limited to that invocation, and the CVE is disputed as a usability problem rather than a security vulnerability.
Summary
What happened
Resource exhaustion in Precomp 0.4.8 allows local users to abort the process by processing a specially crafted input file. A supplied file processed in recursive mode triggers an allocation failure, and the resulting std::bad_alloc exception escapes handling and terminates the process. The demonstrated impact is limited to that invocation, and the CVE is disputed as a usability problem rather than a security vulnerability.
The record
- CVE
- CVE-2023-31854
- Published
- Mar 27, 2024
- Updated
- Aug 20, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 27, 2024CVE publishedPublication date reported by the CVE source.
- Aug 20, 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
No CVSS assessment is available in this record.
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
- precomp-crash.zip reproduction inputproof 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