# CVE-2014-0012: Insecure Temporary File in Jinja2

> Local attackers can escalate privileges by pre-creating temporary directories due to improper handling in the Jinja2 FileSystemBytecodeCache.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-0012, GHSA-fqh9-2qgg-h84h, PYSEC-2014-82, SUSE-SU-2015:1336-1, openSUSE-SU-2019:0244-1, openSUSE-SU-2024:10129-1

## What is CVE-2014-0012?

CVE-2014-0012 is a medium-severity vulnerability in n/a, published on 19 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-264

## Which versions are affected by CVE-2014-0012?

3 open source packages ship an affected version, including jinja2 and Jinja2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jinja2` | PyPI | All versions | 2.7.2 |
| `jinja2` | PyPI | All versions | 2.7.3 |
| `Jinja2` | PyPI | All versions | 2.7.2 |
| `python-Jinja2` | SUSE:Cloud Compute Node for SUSE Linux Enterprise 12 5 | All versions | 2.7.3-4.1 |
| `python-Jinja2` | SUSE:Enterprise Storage 1.0 | All versions | 2.7.3-4.1 |
| `python-Jinja2` | SUSE:Package Hub 12 | All versions | 2.8-2.1 |
| `python-Jinja2` | openSUSE:Tumbleweed | All versions | 2.8-1.4 |

Products: Pocoo Jinja2.

## How do I fix CVE-2014-0012?

Upgrade jinja2 to a fixed version for your release line: 2.7.2 or 2.7.3.

## Is CVE-2014-0012 being exploited?

There is no known exploitation of CVE-2014-0012 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-1402](https://insights.sbomify.com/CVE-2014-1402/): Incorrect Privilege Assignment in Jinja2 (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0012 and fix it if it is affected.

What it is: CVE-2014-0012 is a medium-severity vulnerability in n/a, published on 19 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0012 in the wild and no public exploit code.

Affected packages and fixed versions:
- jinja2 (PyPI): affected all versions; fixed in 2.7.2
- jinja2 (PyPI): affected all versions; fixed in 2.7.3
- Jinja2 (PyPI): affected all versions; fixed in 2.7.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-0012/ (Markdown: https://insights.sbomify.com/CVE-2014-0012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0012
- OSV: https://osv.dev/vulnerability/CVE-2014-0012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-0012/
Summaries are generated and may contain mistakes; the official description above is the record.