CVE-2004-1185: High severity gnu enscript vulnerability
Published Jan 21, 2005
·Updated
Enscript 1.6.3 does not sanitize filenames, which allows remote attackers or local users to execute arbitrary commands via crafted filenames.
Affected Software
7 affected components
GNU Enscript=1.3.0
GNU Enscript=1.5.0
GNU Enscript=1.6.3
GNU Enscript=1.6.0
GNU Enscript=1.6.2
GNU Enscript=1.6.1
GNU Enscript=1.4.0
Remediation
Patch Available
Patch Available
Event History
Jan 21, 2005
CVE Published
05:00 AM
Jan 29, 2005
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2004-1185?
CVE-2004-1185 is considered a high severity vulnerability due to its potential to allow arbitrary command execution.
2
How do I fix CVE-2004-1185?
To fix CVE-2004-1185, ensure you update to a patched version of GNU Enscript that sanitizes filenames.
3
What versions of GNU Enscript are affected by CVE-2004-1185?
CVE-2004-1185 affects GNU Enscript versions 1.3.0, 1.4.0, 1.5.0, and 1.6.0 through 1.6.3.
4
Can local users exploit CVE-2004-1185?
Yes, local users can exploit CVE-2004-1185 due to the lack of filename sanitization.
5
Is remote exploitation possible with CVE-2004-1185?
Yes, remote attackers can exploit CVE-2004-1185 by crafting malicious filenames.