Insufficient Session Expiration in TYPO3's Admin Tool
Published 17 Jun 2022 · Updated 6 Dec 2023
Affected packages
- Affected
- >=9.0.0 <9.5.35
- Fixed in
- 9.5.35
composer require typo3/cms-core:^9.5.35- Affected
- >=10.0.0 <10.4.29
- Fixed in
- 10.4.29
composer require typo3/cms-core:^10.4.29- Affected
- >=11.0.0 <11.5.11
- Fixed in
- 11.5.11
composer require typo3/cms-core:^11.5.11- Affected
- >=10.0.0 <10.4.29
- Fixed in
- 10.4.29
composer require typo3/cms:^10.4.29- Affected
- >=11.0.0 <11.5.11
- Fixed in
- 11.5.11
composer require typo3/cms:^11.5.11Details
> ### Meta
> * CVSS: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L/E:F/RL:O/RC:C (5.6)
Problem
Admin Tool sessions initiated via the TYPO3 backend user interface have not been revoked even if the corresponding user account was degraded to lower permissions or disabled completely. This way, sessions in the admin tool theoretically could have been prolonged without any limit.
Solution
Update to TYPO3 versions 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.
Credits
Thanks to Kien Hoang who reported this issue and to TYPO3 framework merger Ralf Zimmermann and TYPO3 security member Oliver Hader who fixed the issue.
References
Is GHSA-wwjw-r3gj-39fq 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-core, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/typo3/security/advisories/GHSA-wwjw-r3gj-39fq
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-31050
- Linkgithub.com/TYPO3/typo3/commit/592387972912290c135ebecc91768a67f83a3a4d
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2022-31050.yaml
- Packagegithub.com/TYPO3-CMS/core
- Linktypo3.org/security/advisory/typo3-core-sa-2022-005
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.