CVE-2024-22195
Public on
Last Modified:
Description
A cross-site scripting (XSS) flaw was found in Jinja2 due to the xmlattr filter allowing keys with spaces, contrary to XML/HTML attribute standards. If an application accepts user-input keys and renders them for other users, attackers can inject additional attributes, potentially leading to XSS. This misuse of the xmlattr filter enables the injection of arbitrary HTML attributes, bypassing auto-escaping and potentially circumventing attribute validation checks.
Statement
The identified issue is classified as moderate due to a cross-site scripting (XSS) vulnerability in Jinja2. This flaw arises from the xmlattr filter, which permits keys with spaces, contrary to XML/HTML attribute standards. In scenarios where an application accepts user-input keys and renders them for other users, attackers can exploit this vulnerability to inject additional attributes, potentially resulting in XSS attacks. The misuse of the xmlattr filter facilitates the injection of arbitrary HTML attributes, allowing attackers to bypass auto-escaping mechanisms and potentially evade attribute validation checks, posing a moderate security risk.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Additional Information
- This content is not included.Bugzilla 2257854: jinja2: HTML attribute injection when passing user input as keys to xmlattr filter
- Content from cwe.mitre.org is not included.CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- FAQ: Frequently asked questions about CVE-2024-22195
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2024-22195
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2024-22195
Content from github.com is not included.https://github.com/pallets/jinja/releases/tag/3.1.3
Affected Packages and Issued Red Hat Security Errata
| Products / Services | Components | State | Errata |
|---|---|---|---|
| RHUI 4 for RHEL 8 | python-jinja2 | Fixed | RHSA-2024:1878 |
| Red Hat Ansible Automation Platform 1.2 | ansible-tower | Out of support scope | |
| Red Hat Ansible Automation Platform 2 | ansible-lint | Not affected | |
| Red Hat Ansible Automation Platform 2 | python-ansible-compat | Not affected | |
| Red Hat Ansible Automation Platform 2 | python-django-lifecycle | Not affected | |
| Red Hat Ansible Automation Platform 2 | python3-jinja2 | Not affected | |
| Red Hat Ansible Automation Platform 2 | python3x-ansible-compat | Not affected | |
| Red Hat Ansible Automation Platform 2 | python3x-django-lifecycle | Not affected | |
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | python3x-jinja2 | Fixed | RHSA-2024:1057 |
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | automation-controller | Fixed | RHSA-2024:1640 |
| Red Hat Ansible Automation Platform 2.4 for RHEL 9 | python-jinja2 | Fixed | RHSA-2024:1057 |
| Red Hat Ansible Automation Platform 2.4 for RHEL 9 | automation-controller | Fixed | RHSA-2024:1640 |
| Red Hat Ceph Storage 5 | cephadm-ansible | Out of support scope | |
| Red Hat Ceph Storage 6 | cephadm-ansible | Will not fix | |
| Red Hat Ceph Storage 7.1 | rhceph/ceph-nvmeof-cli-rhel9 | Fixed | RHSA-2024:3927 |
| Red Hat Ceph Storage 7.1 | rhceph/ceph-nvmeof-rhel9 | Fixed | RHSA-2024:3927 |
| Red Hat Ceph Storage 7.1 | rhceph/grafana-rhel9 | Fixed | RHSA-2024:3927 |
| Red Hat Ceph Storage 7.1 | rhceph/keepalived-rhel9 | Fixed | RHSA-2024:3927 |
| Red Hat Ceph Storage 7.1 | rhceph/rhceph-7-rhel9 | Fixed | RHSA-2024:3927 |
| Red Hat Ceph Storage 7.1 | rhceph/rhceph-haproxy-rhel9 | Fixed | RHSA-2024:3927 |
| Red Hat Ceph Storage 7.1 | rhceph/rhceph-promtail-rhel9 | Fixed | RHSA-2024:3927 |
| Red Hat Ceph Storage 7.1 | rhceph/snmp-notifier-rhel9 | Fixed | RHSA-2024:3927 |
| Red Hat Developer Hub | rhdh/rhdh-hub-rhel9 | Not affected | |
| Red Hat Discovery 1 | discovery-server-container | Not affected | |
| Red Hat Enterprise Linux 6 | python-jinja2 | Out of support scope | |
| Red Hat Enterprise Linux 7 | python-jinja2 | Out of support scope | |
| Red Hat Enterprise Linux 8 | fence-agents | Fixed | RHSA-2024:2968 |
| Red Hat Enterprise Linux 8 | python27:2.7 | Fixed | RHSA-2024:2987 |
| Red Hat Enterprise Linux 8 | python-jinja2 | Fixed | RHSA-2024:3102 |
| Red Hat Enterprise Linux 8 | rust-srpm-macros | Not affected | |
| Red Hat Enterprise Linux 9 | fence-agents | Fixed | RHSA-2024:2132 |
| Red Hat Enterprise Linux 9 | python-jinja2 | Fixed | RHSA-2024:2348 |
| Red Hat Enterprise Linux 9 | rust-srpm-macros | Not affected | |
| Red Hat Enterprise Linux 9.0 Extended Update Support | fence-agents | Fixed | RHSA-2024:1155 |
| Red Hat OpenShift Container Platform 4 | openshift4-aws-iso | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift4/ztp-site-generate-rhel8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | python-jinja2 | Not affected | |
| Red Hat OpenStack Platform 17.1 for RHEL 9 | openstack-ansible-core | Fixed | RHSA-2024:2733 |
| Red Hat OpenStack Platform 18.0 | python-httpcore | Not affected | |
| Red Hat Quay 3 | quay/quay-rhel8 | Affected | |
| Red Hat Satellite 6 | satellite-capsule:el8/python-jinja2 | Affected | |
| Red Hat Satellite 6 | satellite:el8/python-jinja2 | Affected | |
| Red Hat Satellite 6 | tfm-pulpcore-python-jinja2 | Will not fix | |
| Red Hat Satellite 6.14 for RHEL 8 | python-jinja2 | Fixed | RHSA-2024:1536 |
| Red Hat Satellite 6.15 for RHEL 8 | python-jinja2 | Fixed | RHSA-2024:2010 |
| Red Hat Software Collections | rh-python38-python-jinja2 | Will not fix | |
| Red Hat Storage 3 | gdeploy | Out of support scope |
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
| CVSS v3 Score Breakdown | Red Hat | NVD |
|---|---|---|
| CVSS v3 Base Score | 5.4 | 6.1 |
| Attack Vector | Network | Network |
| Attack Complexity | Low | Low |
| Privileges Required | None | None |
| User Interaction | Required | Required |
| Scope | Unchanged | Changed |
| Confidentiality Impact | Low | Low |
| Integrity Impact | Low | Low |
| Availability Impact | None | None |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
NVD CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
My product is listed as "Out of Support Scope". What does this mean?
Not sure what something means? Check out our Security Glossary.