Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2005-4601

security flaw

Overview

Published
31 Dec 2005
Modified
16 Apr 2026
High CVE
0 Registry packages
18 OS packages
4 Linux distributions
Yes Fix available

Description

The delegate code in ImageMagick 6.2.4.5-0.3 allows remote attackers to execute arbitrary commands via shell metacharacters in a filename that is processed by the display command.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 14 fixes

debian 4 releases · 2 packages

fixed 8
graphicsmagick imagemagick
debian fixes for CVE-2005-4601
ReleasePackageFixed in
11 graphicsmagick 1.1.7-1
11 imagemagick 6:6.2.4.5-0.6
12 graphicsmagick 1.1.7-1
12 imagemagick 6:6.2.4.5-0.6
13 graphicsmagick 1.1.7-1
13 imagemagick 6:6.2.4.5-0.6

2 more rows

echo 1 release · 2 packages

fixed 2
graphicsmagick imagemagick
echo fixes for CVE-2005-4601
ReleasePackageFixed in
graphicsmagick 1.1.7-1
imagemagick 6:6.2.4.5-0.6

openSUSE 1 release · 1 package

fixed 1
imagemagick
openSUSE fixes for CVE-2005-4601
ReleasePackageFixed inAdvisory
Tumbleweed imagemagick +15 7.1.0.8-1.2 openSUSE-SU-2024:10597-1

root.io debian 3 releases · 1 package

fixed 3
rootio-imagemagick
root.io debian fixes for CVE-2005-4601
ReleasePackageFixed in
11 rootio-imagemagick 6:6.2.4.5-0.6
12 rootio-imagemagick 6:6.2.4.5-0.6
13 rootio-imagemagick 6:6.2.4.5-0.6

References

Show all 27 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.