How severe is CVE-2004-1185?

CVE-2004-1185 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2004-1185 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2004-1185?

CVE-2004-1185 primarily affects Gnu Enscript. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2004-1185?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2004-1185 published?

CVE-2004-1185 was published on 2005-01-21 and last updated on 2026-06-16.

CVE-2004-1185

CVE-2004-1185 is a high-severity vulnerability in Gnu Enscript with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 4% (90th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gnu Enscript
Published: 2005-01-21
Last modified: 2026-06-16

Description

Enscript 1.6.3 does not sanitize filenames, which allows remote attackers or local users to execute arbitrary commands via crafted filenames.

Frequently asked questions

What is CVE-2004-1185?: Enscript 1.6.3 does not sanitize filenames, which allows remote attackers or local users to execute arbitrary commands via crafted filenames.
How severe is CVE-2004-1185?: CVE-2004-1185 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2004-1185 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2004-1185?: CVE-2004-1185 primarily affects Gnu Enscript. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2004-1185?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2004-1185 published?: CVE-2004-1185 was published on 2005-01-21 and last updated on 2026-06-16.

References

Affected products (7)

cpe:2.3:a:gnu:enscript:1.3.0:*:*:*:*:*:*:*
cpe:2.3:a:gnu:enscript:1.4.0:*:*:*:*:*:*:*
cpe:2.3:a:gnu:enscript:1.5.0:*:*:*:*:*:*:*
cpe:2.3:a:gnu:enscript:1.6.0:*:*:*:*:*:*:*
cpe:2.3:a:gnu:enscript:1.6.1:*:*:*:*:*:*:*
cpe:2.3:a:gnu:enscript:1.6.2:*:*:*:*:*:*:*
cpe:2.3:a:gnu:enscript:1.6.3:*:*:*:*:*:*:*

More vulnerabilities in Gnu Enscript

CVE-2008-3863 — High (CVSS 7.6): Stack-based buffer overflow in the read_special_escape function in src/psgen.c in GNU Enscript 1.6.1 and 1.6.4 beta,…
CVE-2004-1186 — Medium (CVSS 5.0): Multiple buffer overflows in enscript 1.6.3 allow remote attackers or local users to cause a denial of service…
CVE-2004-1184 — Medium (CVSS 4.6): The EPSF pipe support in enscript 1.6.3 allows remote attackers or local users to execute arbitrary commands via shell…
CVE-2002-0044 — Low (CVSS 3.6): GNU Enscript 1.6.1 and earlier allows local users to overwrite arbitrary files of the Enscript user via a symlink…

All CVEs affecting Gnu Enscript →