CVE-2004-1185
UnknownEPSS 4.48%
Last modified
CVE-2004-1185 is a vulnerability of currently unknown severity. Enscript 1.6.3 does not sanitize filenames, which allows remote attackers or local users to execute arbitrary commands via crafted filenames.. EPSS estimates a 4.48% chance of exploitation in the next 30 days.
Description
Enscript 1.6.3 does not sanitize filenames, which allows remote attackers or local users to execute arbitrary commands via crafted filenames.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Gnu | Enscript | 1.3.0 |
| Gnu | Enscript | 1.4.0 |
| Gnu | Enscript | 1.5.0 |
| Gnu | Enscript | 1.6.0 |
| Gnu | Enscript | 1.6.1 |
| Gnu | Enscript | 1.6.2 |
| Gnu | Enscript | 1.6.3 |
References
- http://www.debian.org/security/2005/dsa-654Patch, Vendor Advisory
- http://www.us-cert.gov/cas/techalerts/TA09-133A.htmlUS Government Resource
- http://www.debian.org/security/2005/dsa-654Patch, Vendor Advisory
- http://www.us-cert.gov/cas/techalerts/TA09-133A.htmlUS Government Resource
Timeline
- Published
- Last Modified
- Status
- Modified
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?
Severity scoring for CVE-2004-1185 is pending analysis. The EPSS model estimates a 4.48% probability of exploitation in the next 30 days.
How do I fix CVE-2004-1185?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2004-1185?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST