typo3-cms/core · Security
Insertion of Sensitive Information into Log File in typo3/cms-core
- GHSA ID
- GHSA-fh99-4pgr-8j99
- CVE ID
- CVE-2022-31047
- Severity
- medium
- Published
- Updated
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
- CVSS v3
- 5.3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Description
Meta
- CVSS:
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C(4.9)
Problem
It has been discovered that system internal credentials or keys (e.g. database credentials) have been logged as plaintext in exception handlers, when logging the complete exception stack trace.
Solution
Update to TYPO3 versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.
Credits
Thanks to Marco Huber who reported this issue and to TYPO3 security member Torben Hansen who fixed the issue.
References
CWEs
- CWE-209 · Generation of Error Message Containing Sensitive Information
- CWE-532 · Insertion of Sensitive Information into Log File
References
- https://github.com/TYPO3/typo3/security/advisories/GHSA-fh99-4pgr-8j99 ↗
- https://nvd.nist.gov/vuln/detail/CVE-2022-31047 ↗
- https://github.com/TYPO3/typo3/commit/c93ea692e7dfef03b7c50fe5437487545bee4d6a ↗
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2022-31047.yaml ↗
- https://typo3.org/security/advisory/typo3-core-sa-2022-002 ↗
- https://github.com/advisories/GHSA-fh99-4pgr-8j99 ↗