Application crash via unbounded GIF LZW loop
Published Apr 4, 2022 · Updated Aug 3, 2024
Heap buffer overflow in HTMLDOC 1.9.14 allows attackers to crash the application when it processes a crafted GIF image. In gif_read_lzw, a cyclic code-table chain leaves code at or above clear_code while each iteration increments sp and copies a table entry beyond its heap buffer. A user or calling application must make HTMLDOC parse the malicious image; the demonstrated consequence is a crash rather than disclosed code execution.
Summary
What happened
Heap buffer overflow in HTMLDOC 1.9.14 allows attackers to crash the application when it processes a crafted GIF image. In gif_read_lzw, a cyclic code-table chain leaves code at or above clear_code while each iteration increments sp and copies a table entry beyond its heap buffer. A user or calling application must make HTMLDOC parse the malicious image; the demonstrated consequence is a crash rather than disclosed code execution.
The record
- CVE
- CVE-2022-24191
- Published
- Apr 4, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-835, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 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
- Crafted GIF crash 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