HighGHSA-3x94-fv5h-5q2cBIT-typo3-2020-15099CVE-2020-15099

Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS

Published 29 Jul 2020 · Updated 8 Jul 2026

Affected packages

typo3/cms-coreComposer

Affected: >=9.0.0 <9.5.20
Fixed in: 9.5.20

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

typo3/cms-coreComposer

Affected: >=10.0.0 <10.4.6
Fixed in: 10.4.6

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

typo3/cmsComposer

Affected: >=10.0.0 <10.4.6
Fixed in: 10.4.6

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

typo3/cmsComposer

Affected: >=9.0.0 <9.5.20
Fixed in: 9.5.20

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

Details

> ### Meta > * CVSS: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C (7.5) > * CWE-20, CWE-200

Problem

In case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used.

In case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions.

Solution

Update to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.

Credits

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

References

TYPO3-CORE-SA-2020-007

Is GHSA-3x94-fv5h-5q2c 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.