CVE-2024-34064: Jinja vulnerable to HTML attribute injection when passing user input as keys to xmlattr filter
Jinja is an extensible templating engine. The xmlattr filter in affected versions of Jinja accepts keys containing non-attribute characters. XML/HTML attributes cannot contain spaces, /, >, or =, as each would then be interpreted as starting a separate attribute. If an application accepts keys (as opposed to only values) as user input, and renders these in pages that other users see as well, an attacker could use this to inject other attributes and perform XSS. The fix for CVE-2024-22195 only addressed spaces but not other characters. Accepting keys as user input is now explicitly considered an unintended use case of the xmlattr filter, and code that does so without otherwise validating the input should be flagged as insecure, regardless of Jinja version. Accepting values as user input continues to be safe. This vulnerability is fixed in 3.1.4.
Other sources
Jinja is vulnerable to cross-site scripting, caused by the acceptance of keys containing non-attribute characters by the xmlattr filter. A remote attacker could exploit this vulnerability to inject other attributes into a Web page which would be executed in a victims Web browser within the security context of the hosting Web site, once the page is viewed. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.
— IBM
Jinja vulnerable to HTML attribute injection when passing user input as keys to xmlattr filter
— Microsoft
The xmlattr filter in affected versions of Jinja accepts keys containing non-attribute characters. XML/HTML attributes cannot contain spaces, /, >, or =, as each would then be interpreted as starting a separate attribute. If an application accepts keys (as opposed to only values) as user input, and renders these in pages that other users see as well, an attacker could use this to inject other attributes and perform XSS. The fix for the previous GHSA-h5c8-rqwp-cp95 CVE-2024-22195 only addressed spaces but not other characters.
Accepting keys as user input is now explicitly considered an unintended use case of the xmlattr filter, and code that does so without otherwise validating the input should be flagged as insecure, regardless of Jinja version. Accepting values as user input continues to be safe.
— GitHub
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/jinja2to a version that resolves this vulnerability.Fixed in 2.10-1ubuntu0.18.04.1+ - Upgrade
Upgrade
ubuntu/jinja2to a version that resolves this vulnerability.Fixed in 2.10.1-2ubuntu0.3 - Upgrade
Upgrade
ubuntu/jinja2to a version that resolves this vulnerability.Fixed in 3.0.3-1ubuntu0.2 - Upgrade
Upgrade
ubuntu/jinja2to a version that resolves this vulnerability.Fixed in 3.1.2-1ubuntu0.23.10.2 - Upgrade
Upgrade
ubuntu/jinja2to a version that resolves this vulnerability.Fixed in 3.1.2-1ubuntu1.1 - Upgrade
Upgrade
ubuntu/jinja2to a version that resolves this vulnerability.Fixed in 2.7.2-2ubuntu0.1~ - Upgrade
Upgrade
ubuntu/jinja2to a version that resolves this vulnerability.Fixed in 3.1.4 - Upgrade
Upgrade
ubuntu/jinja2to a version that resolves this vulnerability.Fixed in 2.8-1ubuntu0.1+ - Upgrade
Upgrade
pip/Jinja2to a version that resolves this vulnerability.Fixed in 3.1.4 - Upgrade
Upgrade
F5 Traffix Systems Signaling Delivery Controllerto a version that resolves this vulnerability.Fixed in 5.2.0 - Upgrade
Upgrade
redhat/jinja2to a version that resolves this vulnerability.Fixed in 3.1.4 - Upgrade
Upgrade
jinjato a version that resolves this vulnerability.Fixed in 3.1.4Patch GHSA-h75v-3vvj-5mfj - Configuration
Do not pass user input as the *keys* parameter to the Jinja `xmlattr` filter. Accepting keys as user input is explicitly considered an unintended use case and code that does so without otherwise validating the input should be flagged as insecure (regardless of Jinja version).}}]}]} }]}
Jinja (xmlattr filter) input_type_for_xmlattr_keys = disallow_keys_as_user_input
Event History
Frequently Asked Questions
What is the severity of CVE-2024-34064?
CVE-2024-34064 has been assigned a vulnerability severity that indicates potential risks related to the xmlattr filter in Jinja.
How do I fix CVE-2024-34064?
To fix CVE-2024-34064, upgrade to the patched versions of Jinja listed in the affected software section.
Which versions of Jinja are affected by CVE-2024-34064?
Versions of Jinja prior to 2.11.4 and 3.1.4 are affected by CVE-2024-34064.
What does CVE-2024-34064 weaken in Jinja?
CVE-2024-34064 weakens the security by allowing keys with non-attribute characters in XML/HTML attributes.
Is my deployment vulnerable to CVE-2024-34064?
If you are using affected versions of Jinja, your deployment is vulnerable to CVE-2024-34064 and should be updated immediately.