- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201408-13
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: Jinja2: Multiple vulnerabilities
     Date: August 29, 2014
     Bugs: #497690
       ID: 201408-13

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
=======
Multiple vulnerabilities have been found in Jinja2, allowing local
attackers to escalate their privileges.

Background
=========
Jinja2 is a template engine written in pure Python.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  dev-python/jinja             < 2.7.3                    >= 2.7.3

Description
==========
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.

Resolution
=========
All Jinja2 users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=dev-python/jinja-2.7.3"

References
=========
[ 1 ] CVE-2014-0012
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-0012
[ 2 ] CVE-2014-1402
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1402

Availability
===========
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/201408-13

Concerns?
========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
======
Copyright 2014 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/

Gentoo: GLSA-201408-13: Jinja2: Multiple vulnerabilities

Multiple vulnerabilities have been found in Jinja2, allowing local attackers to escalate their privileges.

Summary

Multiple vulnerabilities have been discovered in Jinja2. Please review the CVE identifiers referenced below for details.

Resolution

All Jinja2 users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-python/jinja-2.7.3"

References

[ 1 ] CVE-2014-0012 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-0012 [ 2 ] CVE-2014-1402 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1402

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201408-13

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
Severity: Normal
Title: Jinja2: Multiple vulnerabilities
Date: August 29, 2014
Bugs: #497690
ID: 201408-13

Synopsis

Multiple vulnerabilities have been found in Jinja2, allowing local attackers to escalate their privileges.

Background

Jinja2 is a template engine written in pure Python.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-python/jinja < 2.7.3 >= 2.7.3

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.

Related News