Decoder crash via out-of-bounds YUV sample read
Published May 24, 2020 · Updated Aug 4, 2024
Heap buffer over-read in ffjpeg through 2020-02-24 allows remote attackers to crash the decoder through a crafted image file. In jfif_decode at jfif.c:546, pixel conversion reads a four-byte YUV sample immediately beyond its heap allocation and passes the resulting values to yuv_to_rgb. The file must be processed by ffjpeg; the published testcase produces a segmentation fault or sanitizer abort, limiting the demonstrated consequence to a service interrupt.
Summary
What happened
Heap buffer over-read in ffjpeg through 2020-02-24 allows remote attackers to crash the decoder through a crafted image file. In jfif_decode at jfif.c:546, pixel conversion reads a four-byte YUV sample immediately beyond its heap allocation and passes the resulting values to yuv_to_rgb. The file must be processed by ffjpeg; the published testcase produces a segmentation fault or sanitizer abort, limiting the demonstrated consequence to a service interrupt.
The record
- CVE
- CVE-2020-13439
- Published
- May 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2020CVE 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
- heap-buffer-overflow_ffjpeg_d1 testcaseproof 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