rpm package
suse/ImageMagick&distro=SUSE Linux Enterprise Workstation Extension 12 SP5
pkg:rpm/suse/ImageMagick&distro=SUSE%20Linux%20Enterprise%20Workstation%20Extension%2012%20SP5
Vulnerabilities (69)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-20244 | — | < 6.8.8.1-71.162.1 | 6.8.8.1-71.162.1 | Mar 9, 2021 | A flaw was found in ImageMagick in MagickCore/visual-effects.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of math division by zero. The highest threat from this vulnerability is to system availability. | ||
| CVE-2021-20243 | — | < 6.8.8.1-71.162.1 | 6.8.8.1-71.162.1 | Mar 9, 2021 | A flaw was found in ImageMagick in MagickCore/resize.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of math division by zero. The highest threat from this vulnerability is to system availability. | ||
| CVE-2020-27768 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Feb 23, 2021 | In ImageMagick, there is an outside the range of representable values of type 'unsigned int' at MagickCore/quantum-private.h. This flaw affects ImageMagick versions prior to 7.0.9-0. | ||
| CVE-2021-20176 | — | < 6.8.8.1-71.159.2 | 6.8.8.1-71.159.2 | Feb 5, 2021 | A divide-by-zero flaw was found in ImageMagick 6.9.11-57 and 7.0.10-57 in gem.c. This flaw allows an attacker who submits a crafted file that is processed by ImageMagick to trigger undefined behavior through a division by zero. The highest threat from this vulnerability is to sys | ||
| CVE-2020-27755 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | in SetImageExtent() of /MagickCore/image.c, an incorrect image depth size can cause a memory leak because the code which checks for the proper image depth size does not reset the size in the event there is an invalid size. The patch resets the depth to a proper size before throwi | ||
| CVE-2020-27753 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | There are several memory leaks in the MIFF coder in /coders/miff.c due to improper image depth values, which can be triggered by a specially crafted input file. These leaks could potentially lead to an impact to application availability or cause a denial of service. It was origin | ||
| CVE-2020-27752 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | A flaw was found in ImageMagick in MagickCore/quantum-private.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger a heap buffer overflow. This would most likely lead to an impact to application availability, but could potentially lead to an im | ||
| CVE-2020-25664 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | In WriteOnePNGImage() of the PNG coder at coders/png.c, an improper call to AcquireVirtualMemory() and memset() allows for an out-of-bounds write later when PopShortPixel() from MagickCore/quantum-private.h is called. The patch fixes the calls by adding 256 to rowbytes. An attack | ||
| CVE-2020-27757 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | A floating point math calculation in ScaleAnyToQuantum() of /MagickCore/quantum-private.h could lead to undefined behavior in the form of a value outside the range of type unsigned long long. The flaw could be triggered by a crafted input file under certain conditions when it is | ||
| CVE-2020-27754 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | In IntensityCompare() of /magick/quantize.c, there are calls to PixelPacketIntensity() which could return overflowed values to the caller when ImageMagick processes a crafted input file. To mitigate this, the patch introduces and uses the ConstrainPixelIntensity() function, which | ||
| CVE-2020-27751 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | A flaw was found in ImageMagick in MagickCore/quantum-export.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned long long` as well as a shift exponent that is too la | ||
| CVE-2020-27750 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | A flaw was found in ImageMagick in MagickCore/colorspace-private.h and MagickCore/quantum.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned char` and math division | ||
| CVE-2020-25676 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | In CatromWeights(), MeshInterpolate(), InterpolatePixelChannel(), InterpolatePixelChannels(), and InterpolatePixelInfo(), which are all functions in /MagickCore/pixel.c, there were multiple unconstrained pixel offset calculations which were being used with the floor() function. T | ||
| CVE-2020-25675 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | In the CropImage() and CropImageToTiles() routines of MagickCore/transform.c, rounding calculations performed on unconstrained pixel offsets was causing undefined behavior in the form of integer overflow and out-of-range values as reported by UndefinedBehaviorSanitizer. Such issu | ||
| CVE-2020-25674 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | 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 lo | ||
| CVE-2020-25666 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | There are 4 places in HistogramCompare() in MagickCore/histogram.c where an integer overflow is possible during simple math calculations. This occurs in the rgb values and `count` value for a color. The patch uses casts to `ssize_t` type for these calculations, instead of `int`. | ||
| CVE-2020-25665 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 8, 2020 | The PALM image coder at coders/palm.c makes an improper call to AcquireQuantumMemory() in routine WritePALMImage() because it needs to be offset by 256. This can cause a out-of-bounds read later on in the routine. The patch adds 256 to bytes_per_row in the call to AcquireQuantumM | ||
| CVE-2020-27776 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 4, 2020 | A flaw was found in ImageMagick in MagickCore/statistic.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type unsigned long. This would most likely lead to an impact to applicati | ||
| CVE-2020-27775 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 4, 2020 | A flaw was found in ImageMagick in MagickCore/quantum.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type unsigned char. This would most likely lead to an impact to application | ||
| CVE-2020-27774 | — | < 6.8.8.1-71.154.1 | 6.8.8.1-71.154.1 | Dec 4, 2020 | A flaw was found in ImageMagick in MagickCore/statistic.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of a too large shift for 64-bit type `ssize_t`. This would most likely lead to an impact to application |
- CVE-2021-20244Mar 9, 2021affected < 6.8.8.1-71.162.1fixed 6.8.8.1-71.162.1
A flaw was found in ImageMagick in MagickCore/visual-effects.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of math division by zero. The highest threat from this vulnerability is to system availability.
- CVE-2021-20243Mar 9, 2021affected < 6.8.8.1-71.162.1fixed 6.8.8.1-71.162.1
A flaw was found in ImageMagick in MagickCore/resize.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of math division by zero. The highest threat from this vulnerability is to system availability.
- CVE-2020-27768Feb 23, 2021affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
In ImageMagick, there is an outside the range of representable values of type 'unsigned int' at MagickCore/quantum-private.h. This flaw affects ImageMagick versions prior to 7.0.9-0.
- CVE-2021-20176Feb 5, 2021affected < 6.8.8.1-71.159.2fixed 6.8.8.1-71.159.2
A divide-by-zero flaw was found in ImageMagick 6.9.11-57 and 7.0.10-57 in gem.c. This flaw allows an attacker who submits a crafted file that is processed by ImageMagick to trigger undefined behavior through a division by zero. The highest threat from this vulnerability is to sys
- CVE-2020-27755Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
in SetImageExtent() of /MagickCore/image.c, an incorrect image depth size can cause a memory leak because the code which checks for the proper image depth size does not reset the size in the event there is an invalid size. The patch resets the depth to a proper size before throwi
- CVE-2020-27753Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
There are several memory leaks in the MIFF coder in /coders/miff.c due to improper image depth values, which can be triggered by a specially crafted input file. These leaks could potentially lead to an impact to application availability or cause a denial of service. It was origin
- CVE-2020-27752Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
A flaw was found in ImageMagick in MagickCore/quantum-private.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger a heap buffer overflow. This would most likely lead to an impact to application availability, but could potentially lead to an im
- CVE-2020-25664Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
In WriteOnePNGImage() of the PNG coder at coders/png.c, an improper call to AcquireVirtualMemory() and memset() allows for an out-of-bounds write later when PopShortPixel() from MagickCore/quantum-private.h is called. The patch fixes the calls by adding 256 to rowbytes. An attack
- CVE-2020-27757Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
A floating point math calculation in ScaleAnyToQuantum() of /MagickCore/quantum-private.h could lead to undefined behavior in the form of a value outside the range of type unsigned long long. The flaw could be triggered by a crafted input file under certain conditions when it is
- CVE-2020-27754Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
In IntensityCompare() of /magick/quantize.c, there are calls to PixelPacketIntensity() which could return overflowed values to the caller when ImageMagick processes a crafted input file. To mitigate this, the patch introduces and uses the ConstrainPixelIntensity() function, which
- CVE-2020-27751Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
A flaw was found in ImageMagick in MagickCore/quantum-export.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned long long` as well as a shift exponent that is too la
- CVE-2020-27750Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
A flaw was found in ImageMagick in MagickCore/colorspace-private.h and MagickCore/quantum.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned char` and math division
- CVE-2020-25676Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
In CatromWeights(), MeshInterpolate(), InterpolatePixelChannel(), InterpolatePixelChannels(), and InterpolatePixelInfo(), which are all functions in /MagickCore/pixel.c, there were multiple unconstrained pixel offset calculations which were being used with the floor() function. T
- CVE-2020-25675Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
In the CropImage() and CropImageToTiles() routines of MagickCore/transform.c, rounding calculations performed on unconstrained pixel offsets was causing undefined behavior in the form of integer overflow and out-of-range values as reported by UndefinedBehaviorSanitizer. Such issu
- CVE-2020-25674Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
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 lo
- CVE-2020-25666Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
There are 4 places in HistogramCompare() in MagickCore/histogram.c where an integer overflow is possible during simple math calculations. This occurs in the rgb values and `count` value for a color. The patch uses casts to `ssize_t` type for these calculations, instead of `int`.
- CVE-2020-25665Dec 8, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
The PALM image coder at coders/palm.c makes an improper call to AcquireQuantumMemory() in routine WritePALMImage() because it needs to be offset by 256. This can cause a out-of-bounds read later on in the routine. The patch adds 256 to bytes_per_row in the call to AcquireQuantumM
- CVE-2020-27776Dec 4, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
A flaw was found in ImageMagick in MagickCore/statistic.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type unsigned long. This would most likely lead to an impact to applicati
- CVE-2020-27775Dec 4, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
A flaw was found in ImageMagick in MagickCore/quantum.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type unsigned char. This would most likely lead to an impact to application
- CVE-2020-27774Dec 4, 2020affected < 6.8.8.1-71.154.1fixed 6.8.8.1-71.154.1
A flaw was found in ImageMagick in MagickCore/statistic.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of a too large shift for 64-bit type `ssize_t`. This would most likely lead to an impact to application
Page 2 of 4