CVE-2013-4472 json
The openTempFile function in goo/gfile.cc in Xpdf and Poppler 0.24.3 and earlier, when running on a system other than Unix, allows local us…
published 12y ago modified 4mo ago also EUVD-2013-4340
- cvss
- 3.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
The openTempFile function in goo/gfile.cc in Xpdf and Poppler 0.24.3 and earlier, when running on a system other than Unix, allows local users to overwrite arbitrary files via a symlink attack on temporary files with predictable names.
Is CVE-2013-4472 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-4472 updated cvss 1.9
xpdf: insecure temporary file
-
Red Hat Enterprise Linux 5 poppler Red Hat Enterprise Linux 6 poppler, poppler-qt, poppler-qt4, poppler-glib, poppler-utils Red Hat Enterprise Linux 7 poppler, poppler-qt, poppler-cpp, poppler-glib, poppler-demos, poppler-utilsnot affected: vulnerable code not present
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.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.3 | AV:L/AC:M/Au:N/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
seclists.org
/oss-sec/2013/q4/183
mailing-list
-
osvdb.org
/99064
vdb-entry
-
seclists.org
/oss-sec/2013/q4/181
mailing-list
- poppler.freedesktop.org /releases.html
Sources
- CVE List CVE-2013-4472
- NVD CVE-2013-4472
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.