typo3/html-sanitizer
Affected
- introduced
1.0.0, fixed1.5.0(ecosystem)
Fixed versions
1.5.0
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2022-23499
TYPO3 HTML Sanitizer vulnerable to Cross-Site Scripting
Problem
Due to a parsing issue in the upstream package `masterminds/html5`, malicious markup used in a sequence with special HTML CDATA sections cannot be filtered and sanitized. This allows bypassing the cross-site scripting mechanism of `typo3/html-sanitizer`.
Besides that, the upstream package masterminds/html5 provides HTML raw text elements (script, style, noframes, noembed and iframe) as DOMText nodes, which were not processed and sanitized further. None of the mentioned elements were defined in the default builder configuration, that's why only custom behaviors, using one of those tag names, were vulnerable to cross-site scripting.
Solution
Update to typo3/html-sanitizer versions 1.5.0 or 2.1.1 that fix the problem described.
Medium Basis: The source's own band: MODERATE
1.0.0, fixed 1.5.0 (ecosystem)1.5.0
The export has no generic command for this ecosystem.
2.0.0, fixed 2.1.1 (ecosystem)2.1.1
The export has no generic command for this ecosystem.
10.0.0, fixed 10.4.33 (ecosystem)10.4.33
The export has no generic command for this ecosystem.
11.0.0, fixed 11.5.20 (ecosystem)11.5.20
The export has no generic command for this ecosystem.
12.0.0, fixed 12.1.1 (ecosystem)12.1.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0