CVE-2008-6621 json
Unspecified vulnerability in GraphicsMagick before 1.2.3 allows remote attackers to cause a denial of service (crash) via unspecified vecto…
published 2009-04-06 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-6583
- cvss
- 7.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- graphicsmagick Debian 14, Debian 13, Debian 12 1.2.3-1
debian advisories DEBIAN-CVE-2008-6621
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2008-6621 updated cvss 5.0
, CVE-2008-6071, CVE-2008-6072, CVE-2008-6621 multiple security issues in ImageMagick
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.00% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
References
-
secunia.com
/advisories/30549
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2008/1767
vdb-entry, vendor-advisory
- sourceforge.net /project/shownotes.php?release_id=604837
-
osvdb.org
/46258
vdb-entry
- cvs.graphicsmagick.org /cgi-bin/cvsweb.cgi/GraphicsMagick/coders/dpx.c
Sources
- CVE List CVE-2008-6621
- NVD CVE-2008-6621
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.