MediumGHSA-8w3p-qh3x-6gjrBIT-typo3-2022-23504CVE-2022-23504

TYPO3 CMS vulnerable to Sensitive Information Disclosure via YAML Placeholder Expressions in Site Configuration

Published 13 Dec 2022 · Updated 29 Oct 2024

Affected packages

typo3/cms-coreComposer
Affected
>=9.0.0 <9.5.38
Fixed in
9.5.38
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.38
typo3/cms-coreComposer
Affected
>=10.0.0 <10.4.33
Fixed in
10.4.33
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.33
typo3/cms-coreComposer
Affected
>=11.0.0 <11.5.20
Fixed in
11.5.20
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.20
typo3/cms-coreComposer
Affected
>=12.0.0 <12.1.1
Fixed in
12.1.1
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^12.1.1
typo3/cmsComposer
Affected
>=10.0.0 <10.4.33
Fixed in
10.4.33
Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.33
typo3/cmsComposer
Affected
>=11.0.0 <11.5.20
Fixed in
11.5.20
Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.20
typo3/cmsComposer
Affected
>=12.0.0 <12.1.1
Fixed in
12.1.1
Update to the fixed version for your release line, for example:composer require typo3/cms:^12.1.1

Details

> ### CVSS: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:L/E:F/RL:O/RC:C (5.3)

Problem

Due to the lack of handling user-submitted YAML placeholder expressions in the site configuration backend module, attackers could expose sensitive internal information, such as system configuration or HTTP request messages of other website visitors.

A valid backend user account having administrator privileges is needed to exploit this vulnerability.

Solution

Update to TYPO3 versions 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.

Credits

Thanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.

References

Is GHSA-8w3p-qh3x-6gjr 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 signupOr connect GitHub to scan every repo

References

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