CVE-2022-31047 json
Insertion of Sensitive Information into Log File in typo3/cms-core
published 4y ago modified 4mo ago also BIT-typo3-2022-31047 , EUVD-2022-6036 , GHSA-fh99-4pgr-8j99
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
TYPO3 is an open source web content management system. Prior to versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.34 ELTS, 10.4.29, and 11.5.11, system internal credentials or keys (e.g. database credentials) can be logged as plaintext in exception handlers, when logging the complete exception stack trace. TYPO3 versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.34 ELTS, 10.4.29, 11.5.11 contain a fix for the problem.
Patch / fix
- packagist typo3/cms-core 7.6.57, 8.7.47, 9.5.35, 10.4.29, 11.5.11
- packagist typo3/cms 10.4.29, 11.5.11
- bitnami typo3 7.6.57, 8.7.47, 9.5.35, 10.4.29, 11.5.11
- typo3 typo3 7.6.57, 8.7.47, 9.5.35, 10.4.29, 11.5.11
Is CVE-2022-31047 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
1.15% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms-core | >=7.0.0, <7.6.57 >=8.0.0, <8.7.47 >=9.0.0, <9.5.35 >=10.0.0, <10.4.29 >=11.0.0, <11.5.11 |
7.6.57 8.7.47 9.5.35 10.4.29 11.5.11 |
| packagist | typo3/cms | >=10.0.0, <10.4.29 >=11.0.0, <11.5.11 |
10.4.29 11.5.11 |
| bitnami | typo3 | >=7.0.0, <7.6.57 >=8.0.0, <8.7.47 >=9.0.0, <9.5.35 >=10.0.0, <10.4.29 >=11.0.0, <11.5.11 |
7.6.57 8.7.47 9.5.35 10.4.29 11.5.11 |
Affected products
- TYPO3 typo3
Classification
References
-
github.com
/TYPO3/typo3/commit/c93ea692e7dfef03b7c50fe5437487545bee4d6a
web, patch, third-party-advisory
-
typo3.org
/security/advisory/typo3-core-sa-2022-002
web, vendor-advisory
-
github.com
/TYPO3/typo3/security/advisories/GHSA-fh99-4pgr-8j99
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-31047
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2022-31047.yaml
web
-
github.com
/TYPO3-CMS/core
package
Sources
- CVE List CVE-2022-31047
- GitHub Advisory GHSA-fh99-4pgr-8j99
- NVD CVE-2022-31047
- OSV BIT-typo3-2022-31047
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.