Local encoder crash via oversized callback write
Published Jun 14, 2023 · Updated Jan 3, 2025
Stack buffer overflow in fdkaac before 1.0.5 allows local users to crash the encoder by supplying a crafted audio file. The read_callback function in src/main.c writes 19,584 bytes into an 8,192-byte stack buffer while processing the published crash input. A user or workflow must cause fdkaac to encode the malformed local input; the demonstrated result is an AddressSanitizer-detected abort, with no reported data disclosure or code execution.
Summary
What happened
Stack buffer overflow in fdkaac before 1.0.5 allows local users to crash the encoder by supplying a crafted audio file. The read_callback function in src/main.c writes 19,584 bytes into an 8,192-byte stack buffer while processing the published crash input. A user or workflow must cause fdkaac to encode the malformed local input; the demonstrated result is an AddressSanitizer-detected abort, with no reported data disclosure or code execution.
The record
- CVE
- CVE-2023-34823
- Published
- Jun 14, 2023
- Updated
- Jan 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 2023CVE publishedPublication date reported by the CVE source.
- Jan 3, 2025Record 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
- fdkaac issue 55 crash 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