MediumGHSA-47m6-46mj-p235CVE-2022-36020

TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection

Published 16 Sept 2022 · Updated 8 Nov 2023

Affected packages

typo3/html-sanitizerComposer

Affected: >=1.0.0 <1.0.7
Fixed in: 1.0.7

Update to the fixed version for your release line, for example:composer require typo3/html-sanitizer:^1.0.7

typo3/html-sanitizerComposer

Affected: >=2.0.0 <2.0.16
Fixed in: 2.0.16

Update to the fixed version for your release line, for example:composer require typo3/html-sanitizer:^2.0.16

typo3/cms-coreComposer

Affected: >=10.0.0 <10.4.32
Fixed in: 10.4.32

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.32

typo3/cms-coreComposer

Affected: >=11.0.0 <11.5.16
Fixed in: 11.5.16

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.16

typo3/cmsComposer

Affected: >=10.0.0 <10.4.32
Fixed in: 10.4.32

Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.32

typo3/cmsComposer

Affected: >=11.0.0 <11.5.16
Fixed in: 11.5.16

Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.16

Details

> ### 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.

Is GHSA-47m6-46mj-p235 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/html-sanitizer, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.