Process crash via unchecked allocation failure
Published Jan 20, 2023 · Updated Apr 3, 2025
Null pointer dereference in Xiph opusfile 0.9 through 0.12 allows local users to crash a consuming process when memory allocation fails. The op_get_data and op_open1 functions use a null buffer returned by ogg_sync_buffer: the former passes it to a read callback, while the latter passes it to memcpy. Exploitation requires local low-privileged access and an allocation failure; the documented result is a process segfault, while other impacts remain unspecified.
Summary
What happened
Null pointer dereference in Xiph opusfile 0.9 through 0.12 allows local users to crash a consuming process when memory allocation fails. The op_get_data and op_open1 functions use a null buffer returned by ogg_sync_buffer: the former passes it to a read callback, while the latter passes it to memcpy. Exploitation requires local low-privileged access and an allocation failure; the documented result is a process segfault, while other impacts remain unspecified.
The record
- CVE
- CVE-2022-47021
- Published
- Jan 20, 2023
- Updated
- Apr 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 20, 2023CVE publishedPublication date reported by the CVE source.
- Apr 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
No public exploit references are available in this record.
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