Application crash via progressive JPEG heap overwrite
Published Jul 15, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in ok-file-formats through 2020-06-26 allows attackers to crash a consuming application via a crafted JPEG file. The progressive JPEG decoder's ok_jpg_decode_block_progressive() function writes a two-byte value nine bytes beyond a heap allocation while processing the malformed image. Exploitation requires a consuming application to decode the file; the demonstrated result is an AddressSanitizer-detected abort, with no reported data disclosure or code execution.
Summary
What happened
Heap-based buffer overflow in ok-file-formats through 2020-06-26 allows attackers to crash a consuming application via a crafted JPEG file. The progressive JPEG decoder's ok_jpg_decode_block_progressive() function writes a two-byte value nine bytes beyond a heap allocation while processing the malformed image. Exploitation requires a consuming application to decode the file; the demonstrated result is an AddressSanitizer-detected abort, with no reported data disclosure or code execution.
The record
- CVE
- CVE-2020-23707
- Published
- Jul 15, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, 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.
Public exploit references
- Crafted JPEG proof of concept in upstream issue 8proof 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