Not rated
CVE-2020-25674 WriteOnePNGImage() from coders/png.c (the PNG coder) has a for loop with an improper exit condition that can allow an…
Description
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.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| ImageMagick | Versions not published |
References
- bugzilla.redhat.com bugzilla.redhat.com
- [debian-lts-announce] 20210112 [SECURITY] [DLA 2523-1] imagemagick security update lists.debian.org
- [debian-lts-announce] 20230311 [SECURITY] [DLA 3357-1] imagemagick security update lists.debian.org
Timeline
- Published
- Last modified
Other CVEs of ImageMagick
The 69 CVEs of ImageMagick →
CVE-2023-3195
A stack-based buffer overflow issue was found in ImageMagick's coders/tiff.c
Not rated
CVE-2023-34474
A heap-based buffer overflow issue was discovered in ImageMagick's ReadTIM2ImageData() function in coders/tim2.c
Not rated
CVE-2023-34475
A heap use after free issue was discovered in ImageMagick's ReplaceXmpValue() function in MagickCore/profile.c
Not rated
CVE-2023-2157
A heap-based buffer overflow vulnerability was found in the ImageMagick package that can lead to the application…
5.5
Medium