Crash via PSD layer-name stack overflow
Published Feb 6, 2020 · Updated Aug 6, 2024
Stack-based buffer overflow in ImageMagick 6.8.8-5 allows remote attackers to crash image-processing applications via a crafted PSD image. The WritePSDImage function in coders/psd.c formats generated layer names with the expanded L%06ld pattern into an undersized stack buffer while creating PSD output. Processing attacker-supplied image content requires an application or user to invoke PSD handling; memory corruption crashes the process and, under conditions not published by the vendors, permits code execution with that process's privileges.
Summary
What happened
Stack-based buffer overflow in ImageMagick 6.8.8-5 allows remote attackers to crash image-processing applications via a crafted PSD image. The WritePSDImage function in coders/psd.c formats generated layer names with the expanded L%06ld pattern into an undersized stack buffer while creating PSD output. Processing attacker-supplied image content requires an application or user to invoke PSD handling; memory corruption crashes the process and, under conditions not published by the vendors, permits code execution with that process's privileges.
The record
- CVE
- CVE-2014-2030
- Published
- Feb 6, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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.
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