~ / search / GHSA-8w3p-qh3x-6gjr

GHSA-8w3p-qh3x-6gjr

TYPO3 CMS vulnerable to Sensitive Information Disclosure via YAML Placeholder Expressions in Site Configuration

Source: GitHub Advisory Database (reviewed) Moderate CVE-2022-23504

Packages

EcosystemPackageAffectedFixed in
Packagist typo3/cms-core >= 9.0.0, < 9.5.38 9.5.38
Packagist typo3/cms-core >= 10.0.0, < 10.4.33 10.4.33
Packagist typo3/cms-core >= 11.0.0, < 11.5.20 11.5.20
Packagist typo3/cms-core >= 12.0.0, < 12.1.1 12.1.1
Packagist typo3/cms >= 10.0.0, < 10.4.33 10.4.33
Packagist typo3/cms >= 11.0.0, < 11.5.20 11.5.20
Packagist typo3/cms >= 12.0.0, < 12.1.1 12.1.1

Details

As written in the advisory (Markdown source, shown as plain text).

> ### 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](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Configuration/Yaml/YamlApi.html#custom-placeholder-processing) 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 * [TYPO3-CORE-SA-2022-016](https://typo3.org/security/advisory/typo3-core-sa-2022-016)

References

External links from the advisory. They lead to third-party sites.