Skip to content
Fencer Intel
medium 4.0

CVE-2014-1933 json

Pillow Temporary file name leakage

published 2014-04-17 12 y ago modified 2026-06-17 4 mo ago also GHSA-r854-96gq-rfg3 , PYSEC-2014-23 , EUVD-2014-0042

cvss
4.0
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

The (1) JpegImagePlugin.py and (2) EpsImagePlugin.py scripts in Python Image Library (PIL) 1.1.7 and earlier and Pillow before 2.3.1 uses the names of temporary files on the command line, which makes it easier for local users to conduct symlink attacks by listing the processes.

Patch / fix

  • pypi pillow 2.3.1
  • pillow Debian 14, Debian 13, Debian 12 2.4.0-1

debian advisories DEBIAN-CVE-2014-1933

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-2014-1933 updated cvss 2.1

python-imaging: temporary file name exposure in process list

  • Red Hat Enterprise Linux 5 python-imaging Red Hat Enterprise Linux 6 python-imaging, python-imaging-tk, python-imaging-sane Red Hat Enterprise Linux 7 python-pillow, python-pillow-qt, python-pillow-tk, python-pillow-sane
    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.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/python-imaging/Pillow/commit/4e9f367dfd3f04c8f5d23f7f759ec12782e10ee7 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 4.0 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi pillow
<2.3.1
2.3.1

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.