Code execution via unchecked HCOM dictionary size
Published Jul 10, 2023 · Updated Oct 1, 2024
Heap buffer overflow in SoX 14.4.3 allows context-dependent attackers to execute code via a crafted HCOM audio file. The HCOM startread function accepts a dictionary-size field without enforcing the format's 1-to-511-entry limit before parsing dictionary entries. Exploitation requires a user or application to process attacker-supplied HCOM content and can corrupt memory, crash the process, disclose data, or execute code.
Summary
What happened
Heap buffer overflow in SoX 14.4.3 allows context-dependent attackers to execute code via a crafted HCOM audio file. The HCOM startread function accepts a dictionary-size field without enforcing the format's 1-to-511-entry limit before parsing dictionary entries. Exploitation requires a user or application to process attacker-supplied HCOM content and can corrupt memory, crash the process, disclose data, or execute code.
The record
- CVE
- CVE-2023-34318
- Published
- Jul 10, 2023
- Updated
- Oct 1, 2024
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-122, CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2023CVE publishedPublication date reported by the CVE source.
- Oct 1, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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
- SoX HCOM poc_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