GraphicsMagick GraphicsMagick 1.4 2018-12-09

CPE Details

GraphicsMagick GraphicsMagick 1.4 2018-12-09
graphicsmagick
graphicsmagick
1.4
2020-07-14
10h49 +00:00
2020-07-14
10h49 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:graphicsmagick:graphicsmagick:1.4:2018-12-09:*:*:*:*:*:*

Informations

Vendor

graphicsmagick

Product

graphicsmagick

Version

1.4

Update

2018-12-09

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2020-21679 2023-08-21 22h00 +00:00 Buffer Overflow vulnerability in WritePCXImage function in pcx.c in GraphicsMagick 1.4 allows remote attackers to cause a denial of service via converting of crafted image file to pcx format.
5.5
Medium
CVE-2018-20184 2018-12-17 16h00 +00:00 In GraphicsMagick 1.4 snapshot-20181209 Q8, there is a heap-based buffer overflow in the WriteTGAImage function of tga.c, which allows attackers to cause a denial of service via a crafted image file, because the number of rows or columns can exceed the pixel-dimension restrictions of the TGA specification.
6.5
Medium
CVE-2018-20185 2018-12-17 16h00 +00:00 In GraphicsMagick 1.4 snapshot-20181209 Q8 on 32-bit platforms, there is a heap-based buffer over-read in the ReadBMPImage function of bmp.c, which allows attackers to cause a denial of service via a crafted bmp image file. This only affects GraphicsMagick installations with customized BMP limits.
5.3
Medium
CVE-2008-6621 2009-04-06 19h00 +00:00 Unspecified vulnerability in GraphicsMagick before 1.2.3 allows remote attackers to cause a denial of service (crash) via unspecified vectors in DPX images. NOTE: some of these details are obtained from third party information.
7.8
CVE-2007-0770 2007-02-12 19h00 +00:00 Buffer overflow in GraphicsMagick and ImageMagick allows user-assisted remote attackers to cause a denial of service and possibly execute arbitrary code via a PALM image that is not properly handled by the ReadPALMImage function in coders/palm.c. NOTE: this issue is due to an incomplete patch for CVE-2006-5456.
9.3