CVE-2024-56201: Jinja has a sandbox breakout through malicious filenames
A bug in the Jinja compiler allows an attacker that controls both the content and filename of a template to execute arbitrary Python code, regardless of if Jinja's sandbox is used. To exploit the vulnerability, an attacker needs to control both the filename and the contents of a template. Whether that is the case depends on the type of application using Jinja.
Published Dec 23, 2024 · Updated Jan 8, 2025
Affected packages
jinja2
- Ecosystem
- PyPI
- Affected
- >= 3.0.0, <= 3.1.4
- Fixed in
- 3.1.5
- Check
pip show jinja2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
A bug in the Jinja compiler allows an attacker that controls both the content and filename of a template to execute arbitrary Python code, regardless of if Jinja's sandbox is used.
To exploit the vulnerability, an attacker needs to control both the filename and the contents of a template. Whether that is the case depends on the type of application using Jinja. This vulnerability impacts users of applications which execute untrusted templates where the template author can also choose the template filename.
Credited to sleiner, sisp, frenzymadness.
References
- https://github.com/pallets/jinja/security/advisories/GHSA-gmj6-6f8f-6699
- https://github.com/pallets/jinja/releases/tag/3.1.5
- https://nvd.nist.gov/vuln/detail/CVE-2024-56201
- https://github.com/pallets/jinja/issues/1792
- https://github.com/pallets/jinja/commit/767b23617628419ae3709ccfb02f9602ae9fe51f
- https://github.com/advisories/GHSA-gmj6-6f8f-6699
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
