typo3/html-sanitizer
Affected
- introduced
1.0.0, fixed1.5.1(ecosystem)
Fixed versions
1.5.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2023-38500
By-passing Cross-Site Scripting Protection in HTML Sanitizer
> ### CVSS: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C (4.4)
Problem
Due to an encoding issue in the serialization layer, malicious markup nested in a noscript element was not encoded correctly. noscript is disabled in the default configuration, but might have been enabled in custom scenarios. This allows bypassing the cross-site scripting mechanism of `typo3/html-sanitizer`.
Solution
Update to typo3/html-sanitizer versions 1.5.1 or 2.1.2 that fix the problem described.
Credits
Thanks to David Klein and Yaniv Nizry who reported this issue, and to TYPO3 security team members Oliver Hader and Benjamin Franzke who fixed the issue.
References
Medium Basis: The source's own band: MODERATE
1.0.0, fixed 1.5.1 (ecosystem)1.5.1
The export has no generic command for this ecosystem.
2.0.0, fixed 2.1.2 (ecosystem)2.1.2
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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0