Cross-Site Scripting Protection bypass in HTML Sanitizer
TYPO3 html-sanitizer
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| typo3/html-sanitizer Packagist |
|
|
| typo3/cms Packagist |
|
TYPO3 html-sanitizer
| Product | Affected | Fixed in |
|---|---|---|
| typo3/html-sanitizer Packagist |
|
|
| typo3/cms Packagist |
|
≥ 12.0.0 · < 12.1.1
|
HTML sanitizer is written in PHP, aiming to provide XSS-safe markup based on explicitly allowed tags, attributes and values. In versions prior to 1.5.0 or 2.1.1, malicious markup used in a sequence with special HTML CDATA sections cannot be filtered and sanitized due to a parsing issue in the upstream package masterminds/html5. This allows bypassing the cross-site scripting mechanism of typo3/html-sanitizer. 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. This issue has been fixed in versions 1.5.0 and 2.1.1.
From the CVE record · GitHub_M
A parsing issue can let malicious markup containing special HTML CDATA sections bypass sanitization. Cross-site scripting is possible only with custom behavior using script, style, noframes, noembed, or iframe tags; the input does not specify authentication, network access, or user-interaction requirements.
Check installations of typo3/html-sanitizer versions >=1.0.0 <1.5.0 or >=2.0.0 <2.1.1, and typo3/cms versions >=10.0.0 <10.4.33, >=11.0.0 <11.5.20, or >=12.0.0 <12.1.1.