Decoder crash via malformed audio file processing
Published Sep 20, 2021 · Updated Aug 4, 2024
NULL pointer dereference in sela through 20200412 allows local users to crash the decoder by processing a crafted audio file. During decoding, rice::RiceDecoder::process() calls generateDecodedUnsignedInts(), where the crafted file triggers a read through a null address. Exploitation requires user interaction to decode the supplied file; the demonstrated consequence is a segmentation fault that interrupts the decoder process.
Summary
What happened
NULL pointer dereference in sela through 20200412 allows local users to crash the decoder by processing a crafted audio file. During decoding, rice::RiceDecoder::process() calls generateDecodedUnsignedInts(), where the crafted file triggers a read through a null address. Exploitation requires user interaction to decode the supplied file; the demonstrated consequence is a segmentation fault that interrupts the decoder process.
The record
- CVE
- CVE-2021-39545
- Published
- Sep 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 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.
Weakness, pattern, technique
Public exploit references
- SEGV-process-rice_decoder-58.zipproof 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