Pallets Jinja up to 3.1.4 control sequence

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.4$0-$5k0.00

Summaryinfo

A vulnerability was found in Pallets Jinja up to 3.1.4. It has been classified as critical. Affected is an unknown function. This manipulation causes control sequence. The identification of this vulnerability is CVE-2024-56201. The attack can only be executed locally. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical was found in Pallets Jinja up to 3.1.4. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a control sequence vulnerability. The CWE definition for the vulnerability is CWE-150. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Jinja is an extensible templating engine. Prior to 3.1.5, 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. This vulnerability is fixed in 3.1.5.

The advisory is shared at github.com. This vulnerability is known as CVE-2024-56201 since 12/18/2024. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 213487 (SUSE SLED15 / SLES15 / openSUSE 15 Security Update : python-Jinja2 (SUSE-SU-2025:0006-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 3.1.5 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 767b23617628419ae3709ccfb02f9602ae9fe51f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (213487). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍

CVSSv3info

VulDB Meta Base Score: 8.5
VulDB Meta Temp Score: 8.4

VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CNA Base Score: 8.8
CNA Vector (GitHub_M): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Control sequence
CWE: CWE-150 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 213487
Nessus Name: SUSE SLED15 / SLES15 / openSUSE 15 Security Update : python-Jinja2 (SUSE-SU-2025:0006-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Jinja 3.1.5
Patch: 767b23617628419ae3709ccfb02f9602ae9fe51f

Timelineinfo

12/18/2024 🔍
12/23/2024 +5 days 🔍
12/23/2024 +0 days 🔍
09/22/2025 +273 days 🔍

Sourcesinfo

Product: github.com

Advisory: 1792
Status: Confirmed

CVE: CVE-2024-56201 (🔍)
GCVE (CVE): GCVE-0-2024-56201
GCVE (VulDB): GCVE-100-289189

Entryinfo

Created: 12/23/2024 17:31
Updated: 09/22/2025 22:30
Changes: 12/23/2024 17:31 (69), 12/24/2024 03:58 (11), 12/24/2024 14:32 (1), 01/04/2025 11:41 (2), 09/22/2025 22:30 (11)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!