Jinja2 2.10 Template from_string Source code injection ⚔ [Disputed]

Summaryinfo

A vulnerability was found in Jinja2 2.10. It has been classified as critical. This affects the function from_string of the component Template Handler. This manipulation of the argument Source as part of Parameter causes code injection. This vulnerability is handled as CVE-2019-8341. The attack can be initiated remotely. There is not any exploit available. There is ongoing doubt regarding the real existence of this vulnerability.

Detailsinfo

A vulnerability has been found in Jinja2 2.10 and classified as critical. Affected by this vulnerability is the function from_string of the component Template Handler. The manipulation of the argument source as part of a Parameter leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in Jinja2 2.10. The from_string function is prone to Server Side Template Injection (SSTI) where it takes the "source" parameter as a template object, renders it, and then returns it. The attacker can exploit it with {{INJECTION COMMANDS}} in a URI.

The bug was discovered 02/15/2019. The weakness was released 02/15/2019 (Website). It is possible to read the advisory at exploit-db.com. This vulnerability is known as CVE-2019-8341 since 02/15/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.

It is declared as proof-of-concept. The real existence of this vulnerability is still doubted at the moment. The commercial vulnerability scanner Qualys is able to test this issue with plugin 172384 (OpenSUSE Security Update for python-Jinja2 (openSUSE-SU-2019:1395-1)).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Entries connected to this vulnerability are available at VDB-133085 and VDB-133095. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Jinja2

Version

• 2.10

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion