First published: Thu Jan 09 2014(Updated: )
Jinja2, a template engine written in pure python, was found to use /tmp as a default directory for jinja2.bccache.FileSystemBytecodeCache, which is insecure because the /tmp directory is world-writable and the filenames used by FileSystemBytecodeCache are predictable. A malicious local user could exploit this bug to alter output generated by other user's application using Jinja2 or possibly, execute arbitrary code as another user. References: <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734747">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734747</a>
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/python-jinja2 | <2.7.3 | 2.7.3 |
debian/jinja2 | 2.11.3-1 3.1.2-1 3.1.3-1 | |
pip/Jinja2 | <2.7.2 | 2.7.2 |
Python Jinja2 | <=2.7.1 | |
Python Jinja2 | =2.0 | |
Python Jinja2 | =2.0-rc1 | |
Python Jinja2 | =2.1 | |
Python Jinja2 | =2.1.1 | |
Python Jinja2 | =2.2 | |
Python Jinja2 | =2.2.1 | |
Python Jinja2 | =2.3 | |
Python Jinja2 | =2.3.1 | |
Python Jinja2 | =2.4 | |
Python Jinja2 | =2.4.1 | |
Python Jinja2 | =2.5 | |
Python Jinja2 | =2.5.1 | |
Python Jinja2 | =2.5.2 | |
Python Jinja2 | =2.5.3 | |
Python Jinja2 | =2.5.4 | |
Python Jinja2 | =2.5.5 | |
Python Jinja2 | =2.6 | |
Python Jinja2 | =2.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-1402 is classified as a medium severity vulnerability due to its potential for local escalation of privileges.
To fix CVE-2014-1402, upgrade to Jinja2 version 2.7.2 or later.
CVE-2014-1402 affects Jinja2 versions prior to 2.7.2, including versions 2.0 to 2.7.1.
No, CVE-2014-1402 is a local vulnerability that requires local access to exploit.
The impact of CVE-2014-1402 is that a malicious local user could execute arbitrary code with the privileges of the application using Jinja2.