Memory corruption via Huffman encoder buffer overrun
Published Jun 1, 2021 · Updated Aug 4, 2024
Stack buffer overflow in libjpeg-turbo before 2.0.4 allows attackers to overrun memory while losslessly transforming a malformed JPEG. The encode_one_block Huffman routine writes encoded bytes beyond its fixed local buffer when crafted extremely high-frequency coefficients expand unusually. Reachability requires the lossless transformer; the project reports that the overwrite stayed within the stack and produced no crash or visible error.
Summary
What happened
Stack buffer overflow in libjpeg-turbo before 2.0.4 allows attackers to overrun memory while losslessly transforming a malformed JPEG. The encode_one_block Huffman routine writes encoded bytes beyond its fixed local buffer when crafted extremely high-frequency coefficients expand unusually. Reachability requires the lossless transformer; the project reports that the overwrite stayed within the stack and produced no crash or visible error.
The record
- CVE
- CVE-2020-17541
- Published
- Jun 1, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 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
- Malformed JPEG transform 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