3.1.6
16 years ago
1 months ago
Known vulnerabilities in the jinja2 package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for freeVulnerability | Vulnerable Version |
---|---|
Jinja2 is a template engine written in pure Python. It provides a Django inspired non-XML syntax but supports inline expressions and an optional sandboxed environment. Affected versions of this package are vulnerable to Template Injection through the Note: This is only exploitable if the application executes untrusted templates. How to fix Template Injection? Upgrade | [,3.1.6) |
Affected versions of this package are vulnerable to Improper Neutralization when importing a macro in a template whose filename is also a template. This will result in a Note: This is only exploitable when the attacker controls both the content and filename of a template and the application executes untrusted templates. How to fix Improper Neutralization? Upgrade | [,3.1.5) |
Affected versions of this package are vulnerable to Template Injection when an attacker controls the content of a template. This is due to an oversight in the sandboxed environment's method detection when using a stored reference to a malicious string's Note: This is only exploitable through custom filters in an application. How to fix Template Injection? Upgrade | [,3.1.5) |
Jinja2 is a template engine written in pure Python. It provides a Django inspired non-XML syntax but supports inline expressions and an optional sandboxed environment. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) through the Note: This vulnerability derives from an improper fix of CVE-2024-22195, which only addressed spaces but not other characters. How to fix Cross-site Scripting (XSS)? Upgrade | [,3.1.4) |
Jinja2 is a template engine written in pure Python. It provides a Django inspired non-XML syntax but supports inline expressions and an optional sandboxed environment. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the Note
Accepting keys as user input is not common or a particularly intended use case of the How to fix Cross-site Scripting (XSS)? Upgrade | [,3.1.3) |
Jinja2 is a template engine written in pure Python. It provides a Django inspired non-XML syntax but supports inline expressions and an optional sandboxed environment. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). The ReDoS vulnerability is mainly due to the This issue can be mitigated by using Markdown to format user content instead of the urlize filter, or by implementing request timeouts or limiting process memory. PoC by Yeting Li
How to fix Regular Expression Denial of Service (ReDoS)? Upgrade | [,2.11.3) |
Jinja2 is a template engine written in pure Python. It provides a Django inspired non-XML syntax but supports inline expressions and an optional sandboxed environment. Affected versions of this package are vulnerable to Sandbox Escape via the How to fix Sandbox Escape? Upgrade | [,2.10.1) |
Jinja2 is a template engine written in pure Python. It provides a Django inspired non-XML syntax but supports inline expressions and an optional sandboxed environment. Affected versions of this package are vulnerable to Privilege Escalation due to not properly creating 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. How to fix Privilege Escalation? Upgrade | [,2.7.2) |
Affected versions of this package are vulnerable to Insecure Defaults attacks.
The default configuration for bccache.FileSystemBytecodeCache in Jinja2 before 2.7.2 does not properly create temporary files, which allows local users to gain privileges via a crafted .cache file with a name starting with How to fix Insecure Defaults? Upgrade to version | [,2.7.2) |