CVE-2025-57807
BaseFortify
Publication date: 2025-09-05
Last updated on: 2025-11-03
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| imagemagick | imagemagick | From 7.0.11-13 (inc) to 7.1.1-36 (inc) |
| imagemagick | imagemagick | From 7.0.11-13 (inc) to 7.1.1-36 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-122 | 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(). |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
| CWE-131 | The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in ImageMagick versions lower than 14.8.2 involves insecure functions SeekBlob() and WriteBlob(). SeekBlob() allows advancing the stream offset beyond the current end without increasing capacity, and WriteBlob() expands memory incorrectly and copies data beyond allocated memory. On 64-bit builds, this results in a deterministic heap write, potentially corrupting memory. This issue does not require external delegates or policy settings and is fixed in version 14.8.2.
How can this vulnerability impact me? :
The vulnerability can lead to memory corruption through a deterministic heap write, which may cause application instability, crashes, or potentially allow an attacker with high privileges and local access to execute arbitrary code or escalate privileges. However, the CVSS score indicates a low to moderate impact with requirements for high privileges and local access.
What immediate steps should I take to mitigate this vulnerability?
Upgrade ImageMagick to version 14.8.2 or later, as this version contains the fix for the vulnerability.