Vulnerability advisory

GHSA-47m6-46mj-p235

TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection

Published Sep 16, 2022Updated Nov 8, 2023OSV record ↗

Also known as CVE-2022-36020

Severity

CVSS 3.xCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected versions

typo3/html-sanitizer Packagist

All typo3/html-sanitizer advisories →

Affected	Fixed in
`1.0.0` to before 1.0.7	`1.0.7`Advisories →
Also listed as affected (7) `v1.0.0` `v1.0.1` `v1.0.2` `v1.0.3` `v1.0.4` `v1.0.5` `v1.0.6`
`2.0.0` to before 2.0.16	`2.0.16`Advisories →
Also listed as affected (16) `v2.0.0` `v2.0.1` `v2.0.10` `v2.0.11` `v2.0.12` `v2.0.13` `v2.0.14` `v2.0.15` `v2.0.2` `v2.0.3` `v2.0.4` `v2.0.5` `v2.0.6` `v2.0.7` `v2.0.8` `v2.0.9`

typo3/cms-core Packagist

All typo3/cms-core advisories →

Affected	Fixed in
`10.0.0` to before 10.4.32	`10.4.32`Advisories →
Also listed as affected (38) `v10.0.0` `v10.1.0` `v10.2.0` `v10.2.1` `v10.2.2` `v10.3.0` `v10.4.0` `v10.4.1` `v10.4.10` `v10.4.11` `v10.4.12` `v10.4.13` `v10.4.14` `v10.4.15` `v10.4.16` `v10.4.17` `v10.4.18` `v10.4.19` `v10.4.2` `v10.4.20` `v10.4.21` `v10.4.22` `v10.4.23` `v10.4.24` `v10.4.25` `v10.4.26` `v10.4.27` `v10.4.28` `v10.4.29` `v10.4.3` `v10.4.30` `v10.4.31` `v10.4.4` `v10.4.5` `v10.4.6` `v10.4.7` `v10.4.8` `v10.4.9`
`11.0.0` to before 11.5.16	`11.5.16`Advisories →
Also listed as affected (25) `v11.0.0` `v11.1.0` `v11.1.1` `v11.2.0` `v11.3.0` `v11.3.1` `v11.3.2` `v11.3.3` `v11.4.0` `v11.5.0` `v11.5.1` `v11.5.10` `v11.5.11` `v11.5.12` `v11.5.13` `v11.5.14` `v11.5.15` `v11.5.2` `v11.5.3` `v11.5.4` `v11.5.5` `v11.5.6` `v11.5.7` `v11.5.8` `v11.5.9`

typo3/cms Packagist

All typo3/cms advisories →

Affected	Fixed in
`10.0.0` to before 10.4.32	`10.4.32`Advisories →
Also listed as affected (38) `v10.0.0` `v10.1.0` `v10.2.0` `v10.2.1` `v10.2.2` `v10.3.0` `v10.4.0` `v10.4.1` `v10.4.10` `v10.4.11` `v10.4.12` `v10.4.13` `v10.4.14` `v10.4.15` `v10.4.16` `v10.4.17` `v10.4.18` `v10.4.19` `v10.4.2` `v10.4.20` `v10.4.21` `v10.4.22` `v10.4.23` `v10.4.24` `v10.4.25` `v10.4.26` `v10.4.27` `v10.4.28` `v10.4.29` `v10.4.3` `v10.4.30` `v10.4.31` `v10.4.4` `v10.4.5` `v10.4.6` `v10.4.7` `v10.4.8` `v10.4.9`
`11.0.0` to before 11.5.16	`11.5.16`Advisories →
Also listed as affected (25) `v11.0.0` `v11.1.0` `v11.1.1` `v11.2.0` `v11.3.0` `v11.3.1` `v11.3.2` `v11.3.3` `v11.4.0` `v11.5.0` `v11.5.1` `v11.5.10` `v11.5.11` `v11.5.12` `v11.5.13` `v11.5.14` `v11.5.15` `v11.5.2` `v11.5.3` `v11.5.4` `v11.5.5` `v11.5.6` `v11.5.7` `v11.5.8` `v11.5.9`

Description

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/html-sanitizer versions 1.0.7 or 2.0.16 that fix the problem described.

Credits

Thanks to David Klein who reported this issue, and to TYPO3 security team member Oliver Hader who fixed the issue.