Process interruption via overflowing BMP row allocation
Published Feb 11, 2021 · Updated Aug 5, 2024
Integer overflow in the BMP reader in AutoTrace 0.31.1 allows local users to crash image processing via a malformed bitmap. input-bmp.c multiplies the header-controlled biWidth and biBitCnt fields to compute rowbytes without checking for overflow, then passes the resulting size into allocation logic. Exploitation requires a user or invoking application to process the crafted file, and the supported impact is a process-level availability loss.
Summary
What happened
Integer overflow in the BMP reader in AutoTrace 0.31.1 allows local users to crash image processing via a malformed bitmap. input-bmp.c multiplies the header-controlled biWidth and biBitCnt fields to compute rowbytes without checking for overflow, then passes the resulting size into allocation logic. Exploitation requires a user or invoking application to process the crafted file, and the supported impact is a process-level availability loss.
The record
- CVE
- CVE-2019-19004
- Published
- Feb 11, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
No public exploit references are available in this record.
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