CVE-2014-1402: High severity Pocoo Jinja2 vulnerability
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: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734747
Other sources
The default configuration for bccache.FileSystemBytecodeCache in Jinja2 before 2.7.2 does not properly create temporary files, which allows local users to gain privileges via a crafted .cache file with a name starting with jinja2 in /tmp.
— GitHub
The default configuration for bccache.FileSystemBytecodeCache in Jinja2 before 2.7.2 does not properly create temporary files, which allows local users to gain privileges via a crafted .cache file with a name starting with jinja2 in /tmp.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2014-1402?
CVE-2014-1402 is classified as a medium severity vulnerability due to its potential for local escalation of privileges.
How do I fix CVE-2014-1402?
To fix CVE-2014-1402, upgrade to Jinja2 version 2.7.2 or later.
Which versions of Jinja2 are affected by CVE-2014-1402?
CVE-2014-1402 affects Jinja2 versions prior to 2.7.2, including versions 2.0 to 2.7.1.
Can a remote attacker exploit CVE-2014-1402?
No, CVE-2014-1402 is a local vulnerability that requires local access to exploit.
What is the impact of CVE-2014-1402?
The impact of CVE-2014-1402 is that a malicious local user could execute arbitrary code with the privileges of the application using Jinja2.