Skip to content
Fencer Intel
medium 5.5

CVE-2011-2924 json

foomatic-rip filter v4.0.12 and prior used insecurely creates temporary files for storage of PostScript data by rendering the data when the…

published 2019-11-19 6 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2897

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits
0
none known

Summary

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.

Patch / fix

  • foomatic-filters Debian 14, Debian 13, Debian 12 4.0.12-1

debian advisories DEBIAN-CVE-2011-2924

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-2924 updated cvss 1.9

foomatic: foomatic-rip (debug mode) insecure temporary file use in renderer command line by processing PostScript data

  • Red Hat Enterprise Linux 4 foomatic Red Hat Enterprise Linux 5 foomatic Red Hat Enterprise Linux 6 foomatic
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 3.3 AV:L/AC:M/Au:N/C:N/I:P/A:P

Affected products

  • foomatic-filters foomatic-filters

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.