CVE-2020-15099: Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS
First published: Tue Jul 28 2020(Updated: )
> ### 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](https://typo3.org/security/advisory/typo3-core-sa-2020-007)
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| composer/typo3/cms-core | >=10.0.0<10.4.6>=9.0.0<9.5.20 | |
| composer/typo3/cms | >=10.0.0<10.4.6>=9.0.0<9.5.20 | |
| Typo3 Typo3 | >=9.0.0<9.5.20 | |
| Typo3 Typo3 | >=10.0.0<10.4.6 | |
| composer/typo3/cms | >=9.0.0<9.5.20 | 9.5.20 |
| composer/typo3/cms | >=10.0.0<10.4.6 | 10.4.6 |
| composer/typo3/cms-core | >=10.0.0<10.4.6 | 10.4.6 |
| composer/typo3/cms-core | >=9.0.0<9.5.20 | 9.5.20 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://typo3.org/security/advisory/typo3-core-sa-2020-007
- https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-3x94-fv5h-5q2c
- https://nvd.nist.gov/vuln/detail/CVE-2020-15099
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2020-15099.yaml
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2020-15099.yaml
- https://github.com/advisories/GHSA-3x94-fv5h-5q2c (Advisory)
Frequently Asked Questions
What is the vulnerability ID of TYPO3-CORE-SA-2020-007?
The vulnerability ID of TYPO3-CORE-SA-2020-007 is CVE-2020-15099.
What is the severity of CVE-2020-15099?
The severity of CVE-2020-15099 is high (8.1).
What is the affected software version range for TYPO3-CORE-SA-2020-007?
The affected software version range for TYPO3-CORE-SA-2020-007 is greater than or equal to 9.0.0 and less than 9.5.20, and greater than or equal to 10.0.0 and less than 10.4.6.
How can an attacker exploit CVE-2020-15099?
In a case where an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case they obtain a valid HMAC-SHA1 code from another source.
Where can I find more information about TYPO3-CORE-SA-2020-007?
You can find more information about TYPO3-CORE-SA-2020-007 at the TYPO3 security advisory page: https://typo3.org/security/advisory/typo3-core-sa-2020-007
- collector/friends-of-php
- collector/nvd-index
- agent/weakness
- agent/type
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-3x94-fv5h-5q2c
- alias/CVE-2020-15099
- agent/software-canonical-lookup
- agent/severity
- agent/references
- agent/softwarecombine
- agent/description
- collector/nvd-cve
- source/NVD
- agent/author
- collector/github-advisory
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/last-modified-date
- agent/event
- agent/tags
- agent/trending
- package-manager/composer
- vendor/typo3
- canonical/typo3 typo3
- version/typo3 typo3/9.0.0
- version/typo3 typo3/10.0.0