Application crash via four-byte conversion overflow
Published Feb 28, 2022 · Updated Aug 3, 2024
Heap-buffer overflow in AudioFile 1.1.0 allows attackers to crash a consuming application by supplying a crafted audio file. The public report identifies getIndexOfChunk as the trigger and fouBytesToInt at AudioFile.h line 1196 as the fault, but it does not disclose the malformed field or exact failed bounds check. Exploitation requires a consuming application to load the crafted file; the demonstrated consequence is an AddressSanitizer-detected out-of-bounds access and crash.
Summary
What happened
Heap-buffer overflow in AudioFile 1.1.0 allows attackers to crash a consuming application by supplying a crafted audio file. The public report identifies getIndexOfChunk as the trigger and fouBytesToInt at AudioFile.h line 1196 as the fault, but it does not disclose the malformed field or exact failed bounds check. Exploitation requires a consuming application to load the crafted file; the demonstrated consequence is an AddressSanitizer-detected out-of-bounds access and crash.
The record
- CVE
- CVE-2022-25023
- Published
- Feb 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 28, 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
- poc3 malformed audio fileproof 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