Application crash via malformed HCOM dictionary
Published Aug 25, 2022 · Updated Aug 3, 2024
Heap-buffer overflow in SoX of unknown versions allows context-dependent attackers to crash the application with a crafted HCOM file. The startread() HCOM parser in hcom.c processes a malformed dictionary without adequate bounds checking and accesses memory beyond its heap buffer. Exploitation requires a user or consuming application to process the attacker-supplied audio file, and the documented consequence is a process crash.
Summary
What happened
Heap-buffer overflow in SoX of unknown versions allows context-dependent attackers to crash the application with a crafted HCOM file. The startread() HCOM parser in hcom.c processes a malformed dictionary without adequate bounds checking and accesses memory beyond its heap buffer. Exploitation requires a user or consuming application to process the attacker-supplied audio file, and the documented consequence is a process crash.
The record
- CVE
- CVE-2021-23172
- Published
- Aug 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- Sound eXchange Project
- Product
- SoX
- Classifications
- CWE-787, CWE-120, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Not Known
What conditions does exploitation require?
What is affected?
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
- Crafted HCOM crash sampleproof 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