Conversion crash via out-of-bounds heap write
Published Aug 22, 2023 · Updated Oct 7, 2024
Heap buffer overflow in GraphicsMagick 1.4 allows attackers to crash image conversion by supplying a crafted image for PCX output. In coders/pcx.c, WritePCXImage writes a byte immediately past an allocated heap buffer while encoding crafted input as PCX. A user or automated workflow must pass the crafted image to the converter; successful exploitation aborts the conversion process.
Summary
What happened
Heap buffer overflow in GraphicsMagick 1.4 allows attackers to crash image conversion by supplying a crafted image for PCX output. In coders/pcx.c, WritePCXImage writes a byte immediately past an allocated heap buffer while encoding crafted input as PCX. A user or automated workflow must pass the crafted image to the converter; successful exploitation aborts the conversion process.
The record
- CVE
- CVE-2020-21679
- Published
- Aug 22, 2023
- Updated
- Oct 7, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 7, 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.
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.
Public exploit references
- GraphicsMagick bug 619 proof-of-concept inputproof 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