MediumGHSA-fh99-4pgr-8j99BIT-typo3-2022-31047CVE-2022-31047

Insertion of Sensitive Information into Log File in typo3/cms-core

Published 17 Jun 2022 · Updated 16 Feb 2024

Affected packages

typo3/cms-coreComposer

Affected: >=7.0.0 <7.6.57
Fixed in: 7.6.57

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^7.6.57

typo3/cms-coreComposer

Affected: >=8.0.0 <8.7.47
Fixed in: 8.7.47

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^8.7.47

typo3/cms-coreComposer

Affected: >=9.0.0 <9.5.35
Fixed in: 9.5.35

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.35

typo3/cms-coreComposer

Affected: >=10.0.0 <10.4.29
Fixed in: 10.4.29

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.29

typo3/cms-coreComposer

Affected: >=11.0.0 <11.5.11
Fixed in: 11.5.11

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.11

typo3/cmsComposer

Affected: >=10.0.0 <10.4.29
Fixed in: 10.4.29

Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.29

typo3/cmsComposer

Affected: >=11.0.0 <11.5.11
Fixed in: 11.5.11

Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.11

Details

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

Problem

It has been discovered that system internal credentials or keys (e.g. database credentials) have been logged as plaintext in exception handlers, when logging the complete exception stack trace.

Solution

Update to TYPO3 versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.

Credits

Thanks to Marco Huber who reported this issue and to TYPO3 security member Torben Hansen who fixed the issue.

References

TYPO3-CORE-SA-2022-002

Is GHSA-fh99-4pgr-8j99 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.