Codec crash via oversized Huffman table copy
Published Jul 15, 2021 · Updated Aug 4, 2024
Global buffer overflow in ffjpeg through 2020-06-22 allows attackers to crash the codec by processing a crafted JPEG file. In jfif_encode, memcpy reads 272 bytes from the 178-byte STD_HUFTAB_LUMIN_AC global Huffman table, crossing its boundary. Exploitation requires attacker-supplied image input to be processed and is limited to an availability-impacting crash.
Summary
What happened
Global buffer overflow in ffjpeg through 2020-06-22 allows attackers to crash the codec by processing a crafted JPEG file. In jfif_encode, memcpy reads 272 bytes from the 178-byte STD_HUFTAB_LUMIN_AC global Huffman table, crossing its boundary. Exploitation requires attacker-supplied image input to be processed and is limited to an availability-impacting crash.
The record
- CVE
- CVE-2020-23705
- Published
- Jul 15, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 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
- ffjpeg global-buffer-overflow proof of conceptproof 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