Heap corruption via oversized bzip2 MIFF row
Published Sep 28, 2022 · Updated May 21, 2025
Heap buffer overflow in GraphicsMagick before 1.3.38 allows attackers to corrupt heap memory by parsing a crafted MIFF image. ReadMIFFImage trusts the claimed length of a bzip2-compressed row and reads that amount into a fixed-size buffer without validating the length. The flaw affects only builds with BZLIB support and requires GraphicsMagick to process the crafted file, allowing memory corruption and a process crash.
Summary
What happened
Heap buffer overflow in GraphicsMagick before 1.3.38 allows attackers to corrupt heap memory by parsing a crafted MIFF image. ReadMIFFImage trusts the claimed length of a bzip2-compressed row and reads that amount into a fixed-size buffer without validating the length. The flaw affects only builds with BZLIB support and requires GraphicsMagick to process the crafted file, allowing memory corruption and a process crash.
The record
- CVE
- CVE-2022-1270
- Published
- Sep 28, 2022
- Updated
- May 21, 2025
- Vendor
- GraphicsMagick Group
- Product
- GraphicsMagick
- Classifications
- CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 28, 2022CVE publishedPublication date reported by the CVE source.
- May 21, 2025Record 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=GraphicsMagick-1.4.020220326
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
- example.miff heap-overflow 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