MediumGHSA-fv2m-9249-qx85BIT-typo3-2022-36108CVE-2022-36108

TYPO3 CMS vulnerable to Cross-Site Scripting in <f:asset.css> view helper

Published 16 Sept 2022 · Updated 6 Dec 2023

Affected packages

typo3/cms-coreComposer

Affected: >=10.3.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.3.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:H/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C (4.1)

Problem

It has been discovered that the f:asset.css view helper is vulnerable to cross-site scripting when user input is passed as variables to the CSS.

Solution

Update to TYPO3 version 10.4.32 or 11.5.16 that fix the problem described above.

Credits

Thanks to TYPO3 contributor member Frank Nägler who reported this issue and to TYPO3 core & security team member Oliver Hader who fixed the issue.

References

TYPO3-CORE-SA-2022-010

Is GHSA-fv2m-9249-qx85 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/cms-core, 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.