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
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de Composer | typo3/cms | >= 10.0.0, < 10.4.6, >= 9.0.0, < 9.5.20 | 10.4.6, 9.5.20 |
| Paquete de Composer | typo3/cms-core | >= 9.0.0, < 9.5.20, >= 10.0.0, < 10.4.6 | 9.5.20, 10.4.6 |
Referencias
- 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/TYPO3/TYPO3.CMS
- https://typo3.org/security/advisory/typo3-core-sa-2020-007
- Vector CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H- Debilidad (CWE)
CWE-20, CWE-200- Plataforma
- Composer
- Paquete
typo3/cms, typo3/cms-core- Publicada
- 29.07.2020
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-3x94-fv5h-5q2c - CC BY 4.0
Historial de vulnerabilidades: typo3/cms-core
Todas las vulnerabilidades publicadas de este paquete (Paquete de Composer), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 128
- Primera → última
- 09.2018 09.2026
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 1
- Alta 35
- Media 84
- Baja 8
Divulgaciones por año
- 2018: 2
- 2019: 0
- 2020: 13
- 2021: 15
- 2022: 34
- 2023: 3
- 2024: 38
- 2025: 8
- 2026: 15
-
Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.