Show filters
66 Total Results
Displaying 61-66 of 66
Sort by:
Attacker Value
Unknown

CVE-2017-14400

Disclosure Date: September 12, 2017 (last updated November 26, 2024)
In ImageMagick 7.0.7-1 Q16, the PersistPixelCache function in magick/cache.c mishandles the pixel cache nexus, which allows remote attackers to cause a denial of service (NULL pointer dereference in the function GetVirtualPixels in MagickCore/cache.c) via a crafted file.
0
Attacker Value
Unknown

CVE-2017-14324

Disclosure Date: September 12, 2017 (last updated November 26, 2024)
In ImageMagick 7.0.7-1 Q16, a memory leak vulnerability was found in the function ReadMPCImage in coders/mpc.c, which allows attackers to cause a denial of service via a crafted file.
0
Attacker Value
Unknown

CVE-2017-14325

Disclosure Date: September 12, 2017 (last updated November 26, 2024)
In ImageMagick 7.0.7-1 Q16, a memory leak vulnerability was found in the function PersistPixelCache in magick/cache.c, which allows attackers to cause a denial of service (memory consumption in ReadMPCImage in coders/mpc.c) via a crafted file.
0
Attacker Value
Unknown

CVE-2017-14326

Disclosure Date: September 12, 2017 (last updated November 26, 2024)
In ImageMagick 7.0.7-1 Q16, a memory leak vulnerability was found in the function ReadMATImage in coders/mat.c, which allows attackers to cause a denial of service via a crafted file.
0
Attacker Value
Unknown

CVE-2017-14174

Disclosure Date: September 07, 2017 (last updated November 26, 2024)
In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large "length" field in the header but does not contain sufficient backing data, is provided, the loop over "length" would consume huge CPU resources, since there is no EOF check inside the loop.
Attacker Value
Unknown

CVE-2017-14172

Disclosure Date: September 07, 2017 (last updated November 26, 2024)
In coders/ps.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSImage() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large "extent" field in the header but does not contain sufficient backing data, is provided, the loop over "length" would consume huge CPU resources, since there is no EOF check inside the loop.