Unspecified impact via unchecked bit-reader initialization
Published Aug 21, 2021 · Updated Aug 4, 2024
Unchecked return handling in FFmpeg 4.4 allows attackers to cause an unspecified impact via crafted ADTS extradata. The adts_decode_extradata function passes attacker-controlled packet data to init_get_bits without checking whether bit-reader initialization failed. Reaching the flaw requires the ADTS muxer to process crafted codec extradata; neither the CVE record nor the upstream fix identifies a concrete post-failure consequence.
Summary
What happened
Unchecked return handling in FFmpeg 4.4 allows attackers to cause an unspecified impact via crafted ADTS extradata. The adts_decode_extradata function passes attacker-controlled packet data to init_get_bits without checking whether bit-reader initialization failed. Reaching the flaw requires the ADTS muxer to process crafted codec extradata; neither the CVE record nor the upstream fix identifies a concrete post-failure consequence.
The record
- CVE
- CVE-2021-38171
- Published
- Aug 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-252
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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