Decoder crash via out-of-bounds heap reads
Published Feb 8, 2022 · Updated Aug 4, 2024
Heap-buffer over-read in ffjpeg through 01.01.2021 allows attackers to crash the decoder by opening a crafted JPEG file. In jfif_decode at src/jfif.c line 552, two expressions read four-byte values immediately beyond separate one-byte heap allocations. The supplied files trigger the faults during ffjpeg decoding, so user interaction is required and the demonstrated consequence is process termination.
Summary
What happened
Heap-buffer over-read in ffjpeg through 01.01.2021 allows attackers to crash the decoder by opening a crafted JPEG file. In jfif_decode at src/jfif.c line 552, two expressions read four-byte values immediately beyond separate one-byte heap allocations. The supplied files trigger the faults during ffjpeg decoding, so user interaction is required and the demonstrated consequence is process termination.
The record
- CVE
- CVE-2021-44956
- Published
- Feb 8, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 2022CVE 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.
Public exploit references
- decode_poc1.zipproof of concept · demonstrated
- decode_poc2.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