CVE-2025-69204
Integer Overflow in ImageMagick WriteSVGImage Causes Buffer Overflow DoS
Publication date: 2025-12-30
Last updated on: 2025-12-30
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| imagemagick | imagemagick | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-190 | The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in ImageMagick occurs in the WriteSVGImage function where an integer overflow happens due to using an int variable to store number_attributes. This overflow leads to a buffer overflow, which can cause a denial of service (DoS) attack. The issue is fixed in version 7.1.2-12.
How can this vulnerability impact me? :
The vulnerability can cause a denial of service (DoS) attack, meaning that an attacker could exploit it to crash or disrupt the normal operation of ImageMagick, potentially affecting systems or applications that rely on it for image processing.
What immediate steps should I take to mitigate this vulnerability?
Upgrade ImageMagick to version 7.1.2-12 or later, as this version fixes the integer overflow and buffer overflow issues in the WriteSVGImage function.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying if your system is running a vulnerable version of ImageMagick prior to 7.1.2-12. You can check the installed ImageMagick version using the command `magick -version` or `convert -version`. Additionally, monitoring for crashes or denial-of-service symptoms when processing SVG or MVG files may indicate exploitation attempts. Since the vulnerability is triggered by processing crafted MVG files, inspecting logs or network traffic for suspicious MVG or SVG file uploads or conversions could help detect attempts. There are no specific detection commands provided in the resources. [2]