sanitize-html: improper validation of hostnames set by the "allowedIframeHostnames" option can lead to bypass hostname whitelist for iframe element
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.8 | |||
| openshift4/ose-console:v4.8.0-202107010336.p0.git.188a490.assembly.stream | cpe:/a:redhat:openshift:4.8::el8 | RHSA-2021:2438 | 2021-07-27T00:00:00Z |
| openshift4/ose-thanos-rhel8:v4.8.0-202106291913.p0.git.c358e96.assembly.stream | cpe:/a:redhat:openshift:4.8::el8 | RHSA-2021:2438 | 2021-07-27T00:00:00Z |
| Red Hat OpenShift Container Platform 4.9 | |||
| openshift4/ose-prometheus:v4.9.0-202109302016.p0.git.3197fa7.assembly.stream | cpe:/a:redhat:openshift:4.9::el8 | RHSA-2021:3759 | 2021-10-18T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-1141 | Apostrophe Technologies sanitize-html before 2.3.2 does not properly validate the hostnames set by the "allowedIframeHostnames" option when the "allowIframeRelativeUrls" is set to true, which allows attackers to bypass hostname whitelist for iframe element, related using an src value that starts with "/\\example.com". |
Github GHSA |
GHSA-mjxr-4v3x-q3m4 | Improper Input Validation in sanitize-html |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.8% (1.775% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.