CVE-2011-2924
foomatic: foomatic-rip (debug mode) insecure temporary file use in renderer command line by processing PostScript data
Overview
Description
foomatic-rip filter v4.0.12 and prior used insecurely creates temporary files for storage of PostScript data by rendering the data when the debug mode was enabled. This flaw may be exploited by a local attacker to conduct symlink attacks by overwriting arbitrary files accessible with the privileges of the user running the foomatic-rip universal print filter.
Source: OX vulnerability database
Severity
5.5 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Weakness: CWE-59
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 5 fixes
debian 4 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 11 | foomatic-filters | 4.0.12-1 |
| 12 | foomatic-filters | 4.0.12-1 |
| 13 | foomatic-filters | 4.0.12-1 |
| 14 | foomatic-filters | 4.0.12-1 |
echo 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| foomatic-filters | 4.0.12-1 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2011-2924
- access.redhat.com https://access.redhat.com/security/cve/cve-2011-2924
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-2924
- launchpad.net https://launchpad.net/ubuntu/+source/foomatic-filters/4.0.12-1
- lwn.net https://lwn.net/Articles/459979/
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2011-2924
- security-tracker.debian.org https://security-tracker.debian.org/tracker/CVE-2011-2924
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2011-2924
- www.openwall.com https://www.openwall.com/lists/oss-security/2014/02/08/5/1
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.