Sanitize vulnerable to Cross-site Scripting via insufficient neutralization of `style` element 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 | ||||||
|---|---|---|---|---|---|---|---|---|---|
| rgrove | sanitize | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3652-1 | ruby-sanitize security update |
Debian DSA |
DSA-5616-1 | ruby-sanitize security update |
EUVD |
EUVD-2023-2045 | Sanitize is an allowlist-based HTML and CSS sanitizer. Using carefully crafted input, an attacker may be able to sneak arbitrary HTML and CSS through Sanitize starting with version 3.0.0 and prior to version 6.0.2 when Sanitize is configured to use the built-in "relaxed" config or when using a custom config that allows `style` elements and one or more CSS at-rules. This could result in cross-site scripting or other undesired behavior when the malicious HTML and CSS are rendered in a browser. Sanitize 6.0.2 performs additional escaping of CSS in `style` element content, which fixes this issue. Users who are unable to upgrade can prevent this issue by using a Sanitize config that doesn't allow `style` elements, using a Sanitize config that doesn't allow CSS at-rules, or by manually escaping the character sequence `</` as `<\/` in `style` element content. |
Github GHSA |
GHSA-f5ww-cq3m-q3g7 | Sanitize vulnerable to Cross-site Scripting via insufficient neutralization of `style` element content |
Ubuntu USN |
USN-6748-1 | Sanitize vulnerabilities |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.712% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.