Encoder crash via unchecked WAV read length
Published Nov 10, 2021 · Updated Aug 4, 2024
Stack buffer overflow in Xiph Speex 1.2 allows context-dependent attackers to crash speexenc via a crafted WAV file. The reported locus is speexenc.c line 122, where fread copies to_read bytes from the WAV input into the stack-resident input buffer without a shown bounds check. A victim must run the demo encoder on the file; the maintainer could not reproduce the report, so only a process crash is established.
Summary
What happened
Stack buffer overflow in Xiph Speex 1.2 allows context-dependent attackers to crash speexenc via a crafted WAV file. The reported locus is speexenc.c line 122, where fread copies to_read bytes from the WAV input into the stack-resident input buffer without a shown bounds check. A victim must run the demo encoder on the file; the maintainer could not reproduce the report, so only a process crash is established.
The record
- CVE
- CVE-2020-23904
- Published
- Nov 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- sample2.zip crafted WAV 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