ID CVE-2014-1402
Summary 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.
References
Vulnerable Configurations
  • pocoo Jinja2 2.0
    cpe:2.3:a:pocoo:jinja2:2.0
  • pocoo Jinja2 2.0 release candidate 1
    cpe:2.3:a:pocoo:jinja2:2.0:rc1
  • pocoo Jinja2 2.1
    cpe:2.3:a:pocoo:jinja2:2.1
  • pocoo Jinja2 2.1.1
    cpe:2.3:a:pocoo:jinja2:2.1.1
  • pocoo Jinja2 2.2
    cpe:2.3:a:pocoo:jinja2:2.2
  • pocoo Jinja2 2.2.1
    cpe:2.3:a:pocoo:jinja2:2.2.1
  • pocoo Jinja2 2.3
    cpe:2.3:a:pocoo:jinja2:2.3
  • pocoo Jinja2 2.3.1
    cpe:2.3:a:pocoo:jinja2:2.3.1
  • pocoo Jinja2 2.4
    cpe:2.3:a:pocoo:jinja2:2.4
  • pocoo Jinja2 2.4.1
    cpe:2.3:a:pocoo:jinja2:2.4.1
  • pocoo Jinja2 2.5
    cpe:2.3:a:pocoo:jinja2:2.5
  • pocoo Jinja2 2.5.1
    cpe:2.3:a:pocoo:jinja2:2.5.1
  • pocoo Jinja2 2.5.2
    cpe:2.3:a:pocoo:jinja2:2.5.2
  • pocoo Jinja2 2.5.3
    cpe:2.3:a:pocoo:jinja2:2.5.3
  • pocoo Jinja2 2.5.4
    cpe:2.3:a:pocoo:jinja2:2.5.4
  • pocoo Jinja2 2.5.5
    cpe:2.3:a:pocoo:jinja2:2.5.5
  • pocoo Jinja2 2.6
    cpe:2.3:a:pocoo:jinja2:2.6
  • pocoo Jinja2 2.7
    cpe:2.3:a:pocoo:jinja2:2.7
  • pocoo Jinja2 2.7.1
    cpe:2.3:a:pocoo:jinja2:2.7.1
CVSS
Base: 4.4 (as of 20-05-2014 - 07:45)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
LOCAL MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-7166.NASL
    description Version 2.7.3 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 76173
    published 2014-06-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=76173
    title Fedora 20 : python-jinja2-2.7.3-1.fc20 (2014-7166)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-7399.NASL
    description Add patch to fix CVE-2014-1402. Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 76174
    published 2014-06-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=76174
    title Fedora 19 : python-jinja2-2.6-7.fc19 (2014-7399)
  • NASL family Amazon Linux Local Security Checks
    NASL id ALA_ALAS-2014-371.NASL
    description 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.
    last seen 2019-02-21
    modified 2018-04-18
    plugin id 78314
    published 2014-10-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=78314
    title Amazon Linux AMI : python-jinja2 (ALAS-2014-371)
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2014-0747.NASL
    description Updated python-jinja2 packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having Moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. Jinja2 is a template engine written in pure Python. It provides a Django-inspired, non-XML syntax but supports inline expressions and an optional sandboxed environment. It was discovered that Jinja2 did not properly handle bytecode cache files stored in the system's temporary directory. A local attacker could use this flaw to alter the output of an application using Jinja2 and FileSystemBytecodeCache, and potentially execute arbitrary code with the privileges of that application. (CVE-2014-1402) All python-jinja2 users are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. For the update to take effect, all applications using python-jinja2 must be restarted.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 74475
    published 2014-06-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74475
    title CentOS 6 : python-jinja2 (CESA-2014:0747)
  • NASL family Mandriva Local Security Checks
    NASL id MANDRIVA_MDVSA-2014-096.NASL
    description Updated python-jinja2 packages fix security 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 like 'FileSystemBytecodeCache' are often predictable. A malicious user could exploit this bug to execute arbitrary code as another user (CVE-2014-1402).
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 74074
    published 2014-05-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74074
    title Mandriva Linux Security Advisory : python-jinja2 (MDVSA-2014:096)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2014-0747.NASL
    description Updated python-jinja2 packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having Moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. Jinja2 is a template engine written in pure Python. It provides a Django-inspired, non-XML syntax but supports inline expressions and an optional sandboxed environment. It was discovered that Jinja2 did not properly handle bytecode cache files stored in the system's temporary directory. A local attacker could use this flaw to alter the output of an application using Jinja2 and FileSystemBytecodeCache, and potentially execute arbitrary code with the privileges of that application. (CVE-2014-1402) All python-jinja2 users are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. For the update to take effect, all applications using python-jinja2 must be restarted.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 74486
    published 2014-06-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74486
    title RHEL 6 : python-jinja2 (RHSA-2014:0747)
  • NASL family Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2014-0747.NASL
    description From Red Hat Security Advisory 2014:0747 : Updated python-jinja2 packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having Moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. Jinja2 is a template engine written in pure Python. It provides a Django-inspired, non-XML syntax but supports inline expressions and an optional sandboxed environment. It was discovered that Jinja2 did not properly handle bytecode cache files stored in the system's temporary directory. A local attacker could use this flaw to alter the output of an application using Jinja2 and FileSystemBytecodeCache, and potentially execute arbitrary code with the privileges of that application. (CVE-2014-1402) All python-jinja2 users are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. For the update to take effect, all applications using python-jinja2 must be restarted.
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 74483
    published 2014-06-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74483
    title Oracle Linux 6 : python-jinja2 (ELSA-2014-0747)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201408-13.NASL
    description The remote host is affected by the vulnerability described in GLSA-201408-13 (Jinja2: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in Jinja2. Please review the CVE identifiers referenced below for details. Impact : A local attacker could gain escalated privileges via a specially crafted cache file or pre-created temporary directory. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-12
    plugin id 77457
    published 2014-08-30
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=77457
    title GLSA-201408-13 : Jinja2: Multiple vulnerabilities
  • NASL family Solaris Local Security Checks
    NASL id SOLARIS11_JINJA2_20141216.NASL
    description The remote Solaris system is missing necessary patches to address security updates : - 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. (CVE-2014-0012) - 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. (CVE-2014-1402)
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 80649
    published 2015-01-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=80649
    title Oracle Solaris Third-Party Patch Update : jinja2 (multiple_vulnerabilities_in_jinja2)
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20140611_PYTHON_JINJA2_ON_SL6_X.NASL
    description It was discovered that Jinja2 did not properly handle bytecode cache files stored in the system's temporary directory. A local attacker could use this flaw to alter the output of an application using Jinja2 and FileSystemBytecodeCache, and potentially execute arbitrary code with the privileges of that application. (CVE-2014-1402) For the update to take effect, all applications using python-jinja2 must be restarted.
    last seen 2019-02-21
    modified 2018-12-28
    plugin id 74492
    published 2014-06-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74492
    title Scientific Linux Security Update : python-jinja2 on SL6.x i386/x86_64
  • NASL family Ubuntu Local Security Checks
    NASL id UBUNTU_USN-2301-1.NASL
    description It was discovered that Jinja2 incorrectly handled temporary cache files and directories. A local attacker could use this issue to possibly gain privileges. Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-01
    plugin id 76785
    published 2014-07-25
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=76785
    title Ubuntu 12.04 LTS : jinja2 vulnerabilities (USN-2301-1)
redhat via4
advisories
  • bugzilla
    id 1051421
    title CVE-2014-1402 python-jinja2: FileSystemBytecodeCache insecure cache temporary file use
    oval
    AND
    • comment python-jinja2 is earlier than 0:2.2.1-2.el6_5
      oval oval:com.redhat.rhsa:tst:20140747005
    • comment python-jinja2 is signed with Red Hat redhatrelease2 key
      oval oval:com.redhat.rhsa:tst:20140747006
    • OR
      • comment Red Hat Enterprise Linux 6 Client is installed
        oval oval:com.redhat.rhba:tst:20111656001
      • comment Red Hat Enterprise Linux 6 Server is installed
        oval oval:com.redhat.rhba:tst:20111656002
      • comment Red Hat Enterprise Linux 6 Workstation is installed
        oval oval:com.redhat.rhba:tst:20111656003
      • comment Red Hat Enterprise Linux 6 ComputeNode is installed
        oval oval:com.redhat.rhba:tst:20111656004
    rhsa
    id RHSA-2014:0747
    released 2014-06-11
    severity Moderate
    title RHSA-2014:0747: python-jinja2 security update (Moderate)
  • rhsa
    id RHSA-2014:0748
rpms python-jinja2-0:2.2.1-2.el6_5
refmap via4
confirm
gentoo GLSA-201408-13
mandriva MDVSA-2014:096
mlist
  • [El-errata] 20140611 Oracle Linux Security Advisory ELSA-2014-0747
  • [oss-security] 20140110 CVE Request: python-jinja2: arbitrary code execution vulnerability
  • [oss-security] 20140110 Re: CVE Request: python-jinja2: arbitrary code execution vulnerability
secunia
  • 56287
  • 58783
  • 58918
  • 59017
  • 60738
  • 60770
Last major update 06-01-2017 - 21:59
Published 19-05-2014 - 10:55
Last modified 21-12-2017 - 21:29
Back to Top