Decoder crash via unchecked YUV buffer index
Published May 18, 2021 · Updated Aug 4, 2024
Stack-based buffer overflow in ffjpeg through 2020-07-02 allows local users to crash the decoder via a malicious JPEG image. In jfif_decode, dimensions derived from JPEG data select an element beyond the three-pointer yuv_datbuf array before the pointer is dereferenced. Successful exploitation requires a user to pass the crafted file to ffjpeg for decoding and terminates that process with a segmentation fault.
Summary
What happened
Stack-based buffer overflow in ffjpeg through 2020-07-02 allows local users to crash the decoder via a malicious JPEG image. In jfif_decode, dimensions derived from JPEG data select an element beyond the three-pointer yuv_datbuf array before the pointer is dereferenced. Successful exploitation requires a user to pass the crafted file to ffjpeg for decoding and terminates that process with a segmentation fault.
The record
- CVE
- CVE-2020-23851
- Published
- May 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 18, 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.
Public exploit references
- PoC_stackoverflow_ffjpegproof 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