In breve
- CVE-2023-36823 è una vulnerabilità MEDIO (CVSS 6.1) che riguarda sanitize, sanitize (sanitize project).
- Probabilità di sfruttamento nei prossimi 30 giorni (EPSS): 0.71%, superiore al 53.8% delle vulnerabilità.
- Correzione: aggiornare a 6.0.2 o successiva.
| Package | Affected versions | Patched versions |
|---|
| sanitize RubyGems | ≥ 3.0.0, < 6.0.2
| 6.0.2
|
| sanitize | ≥ 3.0.0, < 6.0.2
| 6.0.2
|
Description
Impact
Using carefully crafted input, an attacker may be able to sneak arbitrary HTML and CSS through Sanitize >= 3.0.0, < 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 XSS (cross-site scripting) or other undesired behavior when the malicious HTML and CSS are rendered in a browser.
Patches
Sanitize >= 6.0.2 performs additional escaping of CSS in style element content, which fixes this issue.
Workarounds
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.
Credit
This issue was found by @cure53 during an audit of a project that uses Sanitize and was reported by one of that project's maintainers. Thank you!
NVD description
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free