Skip to content

ImageMagick has a heap-buffer-overflow

Low severity GitHub Reviewed Published Jul 1, 2023 in ImageMagick/ImageMagick • Updated Aug 25, 2025

Package

nuget Magick.NET-Q16-AnyCPU (NuGet)

Affected versions

< 13.2.0

Patched versions

13.2.0
nuget Magick.NET-Q16-HDRI-AnyCPU (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q16-HDRI-OpenMP-arm64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q16-HDRI-OpenMP-x64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q16-HDRI-arm64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q16-HDRI-x64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q16-HDRI-x86 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q16-OpenMP-arm64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q16-OpenMP-x64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q16-arm64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q16-x64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q16-x86 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q8-AnyCPU (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q8-OpenMP-arm64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q8-OpenMP-x64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q8-arm64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q8-x64 (NuGet)
< 13.2.0
13.2.0
nuget Magick.NET-Q8-x86 (NuGet)
< 13.2.0
13.2.0

Description

Summary

While Processing a crafted TIFF file, imagemagick crashes.

Details

Following is the imagemagick version:

imagemagick_git/build_26jun23/bin/magick --version
Version: ImageMagick 7.1.1-13 (Beta) Q16-HDRI x86_64 56f478940:20230625 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC HDRI 
Delegates (built-in): fontconfig freetype jbig jng jpeg lcms lzma pangocairo png tiff webp x xml zlib
Compiler: gcc (4.2)

PoC

issue can be replicated with following command with provided POC file(sent over email):

magick poc.tiff /dev/null

Impact

This can lead to application crash.

Credits

Please give credits to Hardik shah of Vehere (Dawn Treaders team)

References

@urban-warrior urban-warrior published to ImageMagick/ImageMagick Jul 1, 2023
Published to the GitHub Advisory Database Aug 25, 2025
Reviewed Aug 25, 2025
Last updated Aug 25, 2025

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v4 base metrics

Exploitability Metrics
Attack Vector Local
Attack Complexity Low
Attack Requirements None
Privileges Required None
User interaction Passive
Vulnerable System Impact Metrics
Confidentiality None
Integrity None
Availability Low
Subsequent System Impact Metrics
Confidentiality None
Integrity None
Availability None

CVSS v4 base metrics

Exploitability Metrics
Attack Vector: This metric reflects the context by which vulnerability exploitation is possible. This metric value (and consequently the resulting severity) will be larger the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable system. The assumption is that the number of potential attackers for a vulnerability that could be exploited from across a network is larger than the number of potential attackers that could exploit a vulnerability requiring physical access to a device, and therefore warrants a greater severity.
Attack Complexity: This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit. These are conditions whose primary purpose is to increase security and/or increase exploit engineering complexity. A vulnerability exploitable without a target-specific variable has a lower complexity than a vulnerability that would require non-trivial customization. This metric is meant to capture security mechanisms utilized by the vulnerable system.
Attack Requirements: This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack. These differ from security-enhancing techniques/technologies (ref Attack Complexity) as the primary purpose of these conditions is not to explicitly mitigate attacks, but rather, emerge naturally as a consequence of the deployment and execution of the vulnerable system.
Privileges Required: This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability. The method by which the attacker obtains privileged credentials prior to the attack (e.g., free trial accounts), is outside the scope of this metric. Generally, self-service provisioned accounts do not constitute a privilege requirement if the attacker can grant themselves privileges as part of the attack.
User interaction: This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable system. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
Vulnerable System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the VULNERABLE SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the VULNERABLE SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the VULNERABLE SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
Subsequent System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the SUBSEQUENT SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the SUBSEQUENT SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the SUBSEQUENT SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U

EPSS score

Weaknesses

Heap-based Buffer Overflow

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-fff3-4rp7-px97

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.