Process crash via mis-sized trim buffer
Published Nov 24, 2024 · Updated Nov 24, 2024
Heap-based buffer overflow in Imager before 1.025 allows local users to crash a Perl process by trimming a crafted image. The i_trim_rect routine uses a mis-sized temporary buffer, and trim(auto => 1) writes beyond that allocation while processing the image. Exploitation requires the crafted image to reach an application that invokes trim(), after which heap corruption aborts the process; other impact is not established.
Summary
What happened
Heap-based buffer overflow in Imager before 1.025 allows local users to crash a Perl process by trimming a crafted image. The i_trim_rect routine uses a mis-sized temporary buffer, and trim(auto => 1) writes beyond that allocation while processing the image. Exploitation requires the crafted image to reach an application that invokes trim(), after which heap corruption aborts the process; other impact is not established.
The record
- CVE
- CVE-2024-53901
- Published
- Nov 24, 2024
- Updated
- Nov 24, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, CWE-787, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 24, 2024CVE publishedPublication date reported by the CVE source.
- Nov 24, 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
- Imager trim crafted-image reproducerproof 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