TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection
Published 15 Sept 2022 · Updated 6 Dec 2024
Affected packages
- Affected
- >=7.0.0 <7.6.58
- Fixed in
- 7.6.58
composer require typo3/cms-core:^7.6.58- Affected
- >=8.0.0 <8.7.48
- Fixed in
- 8.7.48
composer require typo3/cms-core:^8.7.48- Affected
- >=9.0.0 <9.5.37
- Fixed in
- 9.5.37
composer require typo3/cms-core:^9.5.37- Affected
- >=10.0.0 <10.4.32
- Fixed in
- 10.4.32
composer require typo3/cms-core:^10.4.32- Affected
- >=11.0.0 <11.5.16
- Fixed in
- 11.5.16
composer require typo3/cms-core:^11.5.16Details
> ### Meta
> * CVSS: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C (5.7)
Problem
Due to a parsing issue in upstream package `masterminds/html5`, malicious markup used in a sequence with special HTML comments cannot be filtered and sanitized. This allows to by-pass the cross-site scripting mechanism of `typo3/html-sanitizer`.
Solution
Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.
Credits
Thanks to David Klein who reported this issue, and to TYPO3 security team member Oliver Hader who fixed the issue.
References
Is GHSA-gqqf-g5r7-84vf in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.