Cross-site Scripting in Sanitize
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 |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-4730-1 | ruby-sanitize security update |
EUVD |
EUVD-2020-0503 | In Sanitize (RubyGem sanitize) greater than or equal to 3.0.0 and less than 5.2.1, there is a cross-site scripting vulnerability. When HTML is sanitized using Sanitize's "relaxed" config, or a custom config that allows certain elements, some content in a math or svg element may not be sanitized correctly even if math and svg are not in the allowlist. You are likely to be vulnerable to this issue if you use Sanitize's relaxed config or a custom config that allows one or more of the following HTML elements: iframe, math, noembed, noframes, noscript, plaintext, script, style, svg, xmp. Using carefully crafted input, an attacker may be able to sneak arbitrary HTML through Sanitize, potentially resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser. This has been fixed in 5.2.1. |
Github GHSA |
GHSA-p4x4-rw2p-8j8m | Cross-site Scripting in Sanitize |
Ubuntu USN |
USN-4543-1 | Sanitize vulnerability |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.9% (1.917% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')