typo3/cms-core
Affected
- introduced
9.0.0, fixed9.5.38(ecosystem)
Fixed versions
9.5.38
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-typo3-2022-23504, CVE-2022-23504
TYPO3 CMS vulnerable to Sensitive Information Disclosure via YAML Placeholder Expressions in Site Configuration
> ### CVSS: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:L/E:F/RL:O/RC:C (5.3)
Problem
Due to the lack of handling user-submitted YAML placeholder expressions in the site configuration backend module, attackers could expose sensitive internal information, such as system configuration or HTTP request messages of other website visitors.
A valid backend user account having administrator privileges is needed to exploit this vulnerability.
Solution
Update to TYPO3 versions 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.
Credits
Thanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.
References
Medium Basis: The source's own band: MODERATE
9.0.0, fixed 9.5.38 (ecosystem)9.5.38
The export has no generic command for this ecosystem.
10.0.0, fixed 10.4.33 (ecosystem)10.4.33
The export has no generic command for this ecosystem.
11.0.0, fixed 11.5.20 (ecosystem)11.5.20
The export has no generic command for this ecosystem.
12.0.0, fixed 12.1.1 (ecosystem)12.1.1
The export has no generic command for this ecosystem.
10.0.0, fixed 10.4.33 (ecosystem)10.4.33
The export has no generic command for this ecosystem.
11.0.0, fixed 11.5.20 (ecosystem)11.5.20
The export has no generic command for this ecosystem.
12.0.0, fixed 12.1.1 (ecosystem)12.1.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0