Skip to content
Fencer Intel
medium 6.2

CVE-2014-0012 json

Insecure Temporary File in Jinja2

published 12y ago modified 4mo ago also GHSA-fqh9-2qgg-h84h , PYSEC-2014-82 , EUVD-2014-0024

cvss
6.2
version 3.1, GitHub
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

FileSystemBytecodeCache in Jinja2 2.7.2 does not properly create temporary directories, which allows local users to gain privileges by pre-creating a temporary directory with a user's uid. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-1402.

Patch / fix

  • pypi jinja2 2.7.2, 2.7.3
  • jinja2 Debian 14, Debian 13, Debian 12 2.7.2-2

debian advisories DEBIAN-CVE-2014-0012

  • python-Jinja2 Enterprise Storage 1.0, Cloud Compute Node for SUSE Linux Enterprise 12 5 2.7.3-4.1

suse advisories SUSE-SU-2015:1336-1

  • python-Jinja2 openSUSE Tumbleweed 3.1.6-2.4
  • python-Jinja2 openSUSE Tumbleweed 2.8-1.4
  • python-Jinja2 openSUSE Tumbleweed 3.0.1-3.2
  • python-Jinja2 openSUSE Tumbleweed 3.1.4-1.1
  • python-Jinja2 Package Hub 12 2.8-2.1

opensuse advisories openSUSE-SU-2026:11992-1openSUSE-SU-2024:10129-1openSUSE-SU-2024:11208-1openSUSE-SU-2024:13930-1openSUSE-SU-2019:0244-1

Is CVE-2014-0012 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-0012 updated cvss 4.4

python-jinja2: FileSystemBytecodeCache insecure cache temporary file use, incorrect CVE-2014-1402 fix

  • Red Hat Enterprise Linux 6 python-jinja2 Red Hat Enterprise Linux 7 python-jinja2 Red Hat OpenStack Platform 4 python-jinja2-26 Red Hat Software Collections python27-python-jinja2, python33-python-jinja2
    not 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.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/mitsuhiko/jinja2/commit/acb672b6a179567632e032f547582f30fa2f4aa7 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi jinja2
<2.7.2
<2.7.3
2.7.2
2.7.3

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-377 DEPRECATED: Insecure Temporary File

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.