CVE-2014-0012
First published: Mon May 19 2014(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/Jinja2 | <2.7.2 | 2.7.2 |
| Python Jinja2 | =2.7.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://seclists.org/oss-sec/2014/q1/73
- http://secunia.com/advisories/56328
- http://secunia.com/advisories/60738
- http://www.gentoo.org/security/en/glsa/glsa-201408-13.xml
- https://bugzilla.redhat.com/show_bug.cgi?id=1051421
- https://github.com/mitsuhiko/jinja2/commit/acb672b6a179567632e032f547582f30fa2f4aa7
- https://github.com/mitsuhiko/jinja2/pull/292
- https://github.com/mitsuhiko/jinja2/pull/296
- https://nvd.nist.gov/vuln/detail/CVE-2014-0012
- https://github.com/pallets/jinja2/pull/292
- https://github.com/pallets/jinja2/pull/296
- https://github.com/pallets/jinja/commit/acb672b6a179567632e032f547582f30fa2f4aa7
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734747
- https://github.com/pypa/advisory-database/tree/main/vulns/jinja2/PYSEC-2014-82.yaml
- https://github.com/advisories/GHSA-fqh9-2qgg-h84h (Advisory)
Frequently Asked Questions
What is the severity of CVE-2014-0012?
CVE-2014-0012 is considered a high severity vulnerability due to its potential for privilege escalation.
How do I fix CVE-2014-0012?
To fix CVE-2014-0012, upgrade Jinja2 to a version later than 2.7.2 where this vulnerability has been addressed.
Who is affected by CVE-2014-0012?
Users of Jinja2 version 2.7.2 are affected by CVE-2014-0012.
What type of attack does CVE-2014-0012 facilitate?
CVE-2014-0012 facilitates local privilege escalation attacks.
Is CVE-2014-0012 a result of previous vulnerabilities?
Yes, CVE-2014-0012 is a result of an incomplete fix for CVE-2014-1402.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-fqh9-2qgg-h84h
- alias/CVE-2014-0012
- agent/software-canonical-lookup
- agent/weakness
- agent/references
- agent/last-modified-date
- agent/severity
- agent/description
- agent/author
- agent/event
- collector/github-advisory
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/pip
- vendor/pocoo
- canonical/python jinja2
- version/python jinja2/2.7.2