Skip to content

Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS

High severity GitHub Reviewed Published Jul 28, 2020 in TYPO3/typo3 • Updated Feb 15, 2024

Package

composer typo3/cms (Composer)

Affected versions

>= 10.0.0, < 10.4.6
>= 9.0.0, < 9.5.20

Patched versions

10.4.6
9.5.20
composer typo3/cms-core (Composer)
>= 9.0.0, < 9.5.20
>= 10.0.0, < 10.4.6
9.5.20
10.4.6

Description

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

References

@ohader ohader published to TYPO3/typo3 Jul 28, 2020
Reviewed Jul 29, 2020
Published to the GitHub Advisory Database Jul 29, 2020
Published by the National Vulnerability Database Jul 29, 2020
Last updated Feb 15, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.944%
(84th percentile)

CVE ID

CVE-2020-15099

GHSA ID

GHSA-3x94-fv5h-5q2c

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.