Pulpcore: python-pulpcore: stored cross-site scripting via inline rendering of uploaded html/svg content
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions |
|---|---|---|---|
| Red Hat | Red Hat Ansible Automation Platform 2 | unaffected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unaffected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unaffected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unaffected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unaffected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unaffected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unaffected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unaffected | — |
| Red Hat | Red Hat Satellite 6 | affected | — |
| Red Hat | Red Hat Satellite 6 | affected | — |
| Red Hat | Red Hat Update Infrastructure 4 for Cloud Providers | unaffected | — |
| Red Hat | Red Hat Update Infrastructure 5 | unaffected | — |
| Red Hat | Red Hat Update Infrastructure 5 | unaffected | — |
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Redhat | Ansible Automation Platform |
|
||||||||
| Redhat | Satellite |
|
||||||||
| Redhat | Update Infrastructure |
|
||||||||
| Redhat | Update Infrastructure 4 For Cloud Providers |
|
Vendor Workaround
If immediate update is not possible, administrators can add security headers to the Apache reverse proxy configuration for the /pulp/content/ path. On Satellite, add the following to the Apache configuration (e.g., via a custom .conf file in /etc/httpd/conf.d/ or via a Puppet override): ``` <Location /pulp/content> Header set Content-Disposition "attachment" Header set X-Content-Type-Options "nosniff" Header set Content-Security-Policy "default-src 'none'; sandbox" </Location> ``` This forces all content downloads rather than inline rendering, and blocks script execution even if Content-Disposition is somehow bypassed. After applying, restart Apache: ```systemctl restart httpd``` Alternatively, restrict file upload permissions in Satellite to only trusted users who require content management capabilities.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.235% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat update Infrastructure
Redhat update Infrastructure 4 For Cloud Providers |
|
| Vendors & Products |
Redhat update Infrastructure
Redhat update Infrastructure 4 For Cloud Providers |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in pulpcore's content serving application. Files uploaded to Pulp file-type repositories are served with their original content type (e.g., text/html for .html files, image/svg+xml for .svg files) and without a Content-Disposition: attachment header when using local filesystem storage. An authenticated user or attacker with content upload permissions can upload a specially crafted HTML or SVG file containing JavaScript, which executes in the browser of any user who visits the file URL, resulting in stored cross-site scripting (XSS) in the context of the host application. | |
| Title | Pulpcore: python-pulpcore: stored cross-site scripting via inline rendering of uploaded html/svg content | |
| First Time appeared |
Redhat
Redhat ansible Automation Platform Redhat rhui Redhat satellite |
|
| Weaknesses | CWE-79 | |
| CPEs | cpe:/a:redhat:ansible_automation_platform:2 cpe:/a:redhat:rhui:4::el8 cpe:/a:redhat:rhui:5::el9 cpe:/a:redhat:satellite:6 |
|
| Vendors & Products |
Redhat
Redhat ansible Automation Platform Redhat rhui Redhat satellite |
|
| References |
| |
| Metrics |
cvssV3_1
|