Skip to content

TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection

Moderate severity GitHub Reviewed Published Sep 13, 2022 in TYPO3/typo3 • Updated Jan 10, 2023

Package

composer typo3/cms-core (Composer)

Affected versions

>= 7.0.0, <= 7.6.57
>= 8.0.0, <= 8.7.47
>= 9.0.0, <= 9.5.36
>= 10.0.0, <= 10.4.31
>= 11.0.0, <= 11.5.15

Patched versions

7.6.58
8.7.48
9.5.37
10.4.32
11.5.16

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

References

@ohader ohader published to TYPO3/typo3 Sep 13, 2022
Published to the GitHub Advisory Database Sep 15, 2022
Reviewed Sep 15, 2022
Last updated Jan 10, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Weaknesses

No CWEs

CVE ID

No known CVE

GHSA ID

GHSA-gqqf-g5r7-84vf

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.