Undefined behavior via depleted JPEG code buffer
Published Apr 15, 2022 · Updated Aug 3, 2024
Incorrect calculation in stb 2.27 allows context-dependent attackers to trigger undefined behavior through a crafted JPEG file. In stbi__jpeg_decode_block_prog_ac, exhausted code bits become negative, so stbi__grow_buffer_unsafe shifts a 32-bit value by more than 32 bits. An application must process the crafted image; the public reproducer demonstrates sanitizer-detected undefined behavior, but no further impact has been demonstrated.
Summary
What happened
Incorrect calculation in stb 2.27 allows context-dependent attackers to trigger undefined behavior through a crafted JPEG file. In stbi__jpeg_decode_block_prog_ac, exhausted code bits become negative, so stbi__grow_buffer_unsafe shifts a 32-bit value by more than 32 bits. An application must process the crafted image; the public reproducer demonstrates sanitizer-detected undefined behavior, but no further impact has been demonstrated.
The record
- CVE
- CVE-2022-28048
- Published
- Apr 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-682
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- UBSAN shift-too-large reproducer archiveproof 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