Advisory

GHSA-47m6-46mj-p235

Also known as: CVE-2022-36020

Summary

TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-09-16 18:50 UTC
Modified
2023-11-08 04:09 UTC

Affected packages and fixes

typo3/html-sanitizer

Packagist · All systems

Affected

  • introduced 1.0.0, fixed 1.0.7 (ecosystem)

Fixed versions

1.0.7

Fix

The export has no generic command for this ecosystem.

typo3/html-sanitizer

Packagist · All systems

Affected

  • introduced 2.0.0, fixed 2.0.16 (ecosystem)

Fixed versions

2.0.16

Fix

The export has no generic command for this ecosystem.

typo3/cms-core

Packagist · All systems

Affected

  • introduced 10.0.0, fixed 10.4.32 (ecosystem)

Fixed versions

10.4.32

Fix

The export has no generic command for this ecosystem.

typo3/cms-core

Packagist · All systems

Affected

  • introduced 11.0.0, fixed 11.5.16 (ecosystem)

Fixed versions

11.5.16

Fix

The export has no generic command for this ecosystem.

typo3/cms

Packagist · All systems

Affected

  • introduced 10.0.0, fixed 10.4.32 (ecosystem)

Fixed versions

10.4.32

Fix

The export has no generic command for this ecosystem.

typo3/cms

Packagist · All systems

Affected

  • introduced 11.0.0, fixed 11.5.16 (ecosystem)

Fixed versions

11.5.16

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences