ImageMagick: heap-based buffer overflow in WriteOnePNGImage in coders/png.c
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | ImageMagick | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2523-1 | imagemagick security update |
Debian DLA |
DLA-3357-1 | imagemagick security update |
EUVD |
EUVD-2020-18336 | WriteOnePNGImage() from coders/png.c (the PNG coder) has a for loop with an improper exit condition that can allow an out-of-bounds READ via heap-buffer-overflow. This occurs because it is possible for the colormap to have less than 256 valid values but the loop condition will loop 256 times, attempting to pass invalid colormap data to the event logger. The patch replaces the hardcoded 256 value with a call to MagickMin() to ensure the proper value is used. This could impact application availability when a specially crafted input file is processed by ImageMagick. This flaw affects ImageMagick versions prior to 7.0.8-68. |
Ubuntu USN |
USN-4988-1 | ImageMagick vulnerabilities |
Ubuntu USN |
USN-5335-1 | ImageMagick vulnerabilities |
Ubuntu USN |
USN-7068-1 | ImageMagick vulnerabilities |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.0% (1.028% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.