CVE-2022-31047: Insertion of Sensitive Information into Log File in typo3/cms-core
5.3
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.64361%
CWE
Published
6/17/2022
Updated
7/24/2023
KEV Status
No
Technology
PHP
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| typo3/cms-core | composer | >= 7.0.0, < 7.6.57 | 7.6.57 |
| typo3/cms-core | composer | >= 8.0.0, < 8.7.47 | 8.7.47 |
| typo3/cms-core | composer | >= 9.0.0, < 9.5.35 | 9.5.35 |
| typo3/cms-core | composer | >= 10.0.0, < 10.4.29 | 10.4.29 |
| typo3/cms-core | composer | >= 11.0.0, < 11.5.11 | 11.5.11 |
| typo3/cms | composer | >= 10.0.0, < 10.4.29 | 10.4.29 |
| typo3/cms | composer | >= 11.0.0, < 11.5.11 | 11.5.11 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from the writeLogEntries method in AbstractExceptionHandler.php, which handled exception logging. The pre-patch version unconditionally added the exception object (including stack traces) to log contexts. The commit c93ea69 introduced a $logExceptionStackTrace flag to control this behavior, indicating this was the vulnerable point. The CWE-532 (log insertion of sensitive info) directly maps to this function's pre-patch behavior of logging raw exception data containing credentials.