Information Disclosure in TYPO3 Page Tree
Published 8 Oct 2024 · Updated 9 Oct 2024
Affected packages
- Affected
- >=13.0.0 <13.3.1
- Fixed in
- 13.3.1
composer require typo3/cms-backend:^13.3.1- Affected
- >=12.0.0 <12.4.21
- Fixed in
- 12.4.21
composer require typo3/cms-backend:^12.4.21- Affected
- >=11.0.0 <11.5.40
- Fixed in
- 11.5.40
composer require typo3/cms-backend:^11.5.40- Affected
- >=10.0.0 <10.4.46
- Fixed in
- 10.4.46
composer require typo3/cms-backend:^10.4.46Details
Problem
Backend users could see items in the backend page tree without having access if the mounts pointed to pages restricted for their user/group, or if no mounts were configured but the pages allowed access to "everybody." However, affected users could not manipulate these pages.
Solution
Update to TYPO3 versions 10.4.46 ELTS, 11.5.40 LTS, 12.4.21 LTS, 13.3.1 that fix the problem described.
Credits
Thanks to Peter Schuler who reported this issue and to TYPO3 core & security team member Oliver Hader who fixed the issue.
Is GHSA-rf5m-h8q9-9w6q in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-backend, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/typo3/security/advisories/GHSA-rf5m-h8q9-9w6q
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-47780
- Linkgithub.com/TYPO3-CMS/backend/commit/8b024b08a2c7071a2f2ff7c758766e4e9273f83c
- Linkgithub.com/TYPO3-CMS/backend/commit/9ae1ef969b63292a13f80955a95713cabd45cc22
- Linkgithub.com/TYPO3-CMS/backend/commit/a7b3c924014ada61632cd5e3fb9825fcc86c5719
- Packagegithub.com/TYPO3-CMS/backend
- Linktypo3.org/security/advisory/typo3-core-sa-2024-012
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.