Memory leak via late TIFF channel validation
Published Aug 26, 2022 · Updated Aug 3, 2024
Memory leak in ImageMagick 7.0.11-5 allows local users to consume process memory by supplying a crafted TIFF file. In ReadTIFFImage, the TIFF channel-count limit is checked only after AcquireQuantumInfo and pixel-buffer setup allocate memory, and the error path returns without releasing those allocations. Triggering requires a user or application to process the TIFF; each failed decode leaves the quantum allocations live until the process exits.
Summary
What happened
Memory leak in ImageMagick 7.0.11-5 allows local users to consume process memory by supplying a crafted TIFF file. In ReadTIFFImage, the TIFF channel-count limit is checked only after AcquireQuantumInfo and pixel-buffer setup allocate memory, and the error path returns without releasing those allocations. Triggering requires a user or application to process the TIFF; each failed decode leaves the quantum allocations live until the process exits.
The record
- CVE
- CVE-2021-3574
- Published
- Aug 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- ImageMagick Studio LLC
- Product
- ImageMagick
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in ImageMagick-7.0.11-8, ImageMagick-6.9.12-8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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 TIFF LeakSanitizer 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