typo3/cms-core
Affected
- introduced
9.0.0, fixed9.5.20(ecosystem)
Fixed versions
9.5.20
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-typo3-2020-15099, CVE-2020-15099
Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS
> ### 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
High Basis: The source's own band: HIGH
9.0.0, fixed 9.5.20 (ecosystem)9.5.20
The export has no generic command for this ecosystem.
10.0.0, fixed 10.4.6 (ecosystem)10.4.6
The export has no generic command for this ecosystem.
10.0.0, fixed 10.4.6 (ecosystem)10.4.6
The export has no generic command for this ecosystem.
9.0.0, fixed 9.5.20 (ecosystem)9.5.20
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0