CVE-2022-31047
First published: Tue Jun 14 2022(Updated: )
> ### 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 * [TYPO3-CORE-SA-2022-002](https://typo3.org/security/advisory/typo3-core-sa-2022-002)
Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Typo3 Typo3 | >=7.0.0<7.6.57 | |
| Typo3 Typo3 | >=8.0.0<8.7.47 | |
| Typo3 Typo3 | >=9.0.0<9.5.35 | |
| Typo3 Typo3 | >=10.0.0<10.4.29 | |
| Typo3 Typo3 | >=11.0.0<11.5.11 | |
| composer/typo3/cms | >=10.0.0<10.4.29>=11.0.0<11.5.11 | |
| composer/typo3/cms-core | >=10.0.0<10.4.29>=11.0.0<11.5.11 | |
| composer/typo3/cms | >=11.0.0<11.5.11 | 11.5.11 |
| composer/typo3/cms | >=10.0.0<10.4.29 | 10.4.29 |
| composer/typo3/cms-core | >=11.0.0<11.5.11 | 11.5.11 |
| composer/typo3/cms-core | >=10.0.0<10.4.29 | 10.4.29 |
| composer/typo3/cms-core | >=9.0.0<9.5.35 | 9.5.35 |
| composer/typo3/cms-core | >=8.0.0<8.7.47 | 8.7.47 |
| composer/typo3/cms-core | >=7.0.0<7.6.57 | 7.6.57 |
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-2022-002
- 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://github.com/advisories/GHSA-fh99-4pgr-8j99 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2022-31047?
The severity of CVE-2022-31047 is medium with a CVSS score of 6.5.
How does CVE-2022-31047 impact TYPO3?
CVE-2022-31047 can lead to information disclosure through the logging of system internal credentials or keys.
Which versions of TYPO3 are affected by CVE-2022-31047?
TYPO3 versions 7.0.0 to 7.6.57, 8.0.0 to 8.7.47, 9.0.0 to 9.5.35, 10.0.0 to 10.4.29, and 11.0.0 to 11.5.11 are affected by CVE-2022-31047.
How can I fix CVE-2022-31047?
To fix CVE-2022-31047, upgrade to TYPO3 version 7.6.58, 8.7.48, 9.5.36, 10.4.30, or 11.5.12.
Where can I find more information about CVE-2022-31047?
You can find more information about CVE-2022-31047 in the TYPO3 security advisory TYPO3-CORE-SA-2022-002.
- collector/friends-of-php
- collector/github-advisory-latest
- alias/GHSA-fh99-4pgr-8j99
- alias/CVE-2022-31047
- collector/github-advisory
- collector/nvd-index
- collector/nvd-cve
- agent/severity
- agent/weakness
- agent/author
- agent/type
- agent/event
- agent/description
- agent/remedy
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- agent/references
- agent/tags
- collector/nvd-api
- agent/software-canonical-lookup-request
- package-manager/composer
- vendor/typo3
- canonical/typo3 typo3
- version/typo3 typo3/7.0.0
- version/typo3 typo3/8.0.0
- version/typo3 typo3/9.0.0
- version/typo3 typo3/10.0.0
- version/typo3 typo3/11.0.0