TYPO3 HTML Sanitizer vulnerable to Cross-Site Scripting
### Problem Due to a parsing issue in the upstream package [`masterminds/html5`](https://packagist.org/packages/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`](https://packagist.org/packages/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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-23499US | medium6.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… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2022-23499.yamlWEB
- https://github.com/TYPO3/html-sanitizerPACKAGE
- https://github.com/TYPO3/html-sanitizer/pull/105WEB
- https://github.com/TYPO3/html-sanitizer/pull/106WEB
- https://github.com/TYPO3/html-sanitizer/releases/tag/v1.5.0WEB
- https://github.com/TYPO3/html-sanitizer/releases/tag/v2.1.1WEB
- https://github.com/TYPO3/html-sanitizer/security/advisories/GHSA-hvwx-qh2h-xcfjWEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-23499ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan