HighGHSA-82vp-jr39-4j2j
TYPO3 Security Misconfiguration in Frontend Session Handling
Published 30 May 2024 · Updated 5 Dec 2024
Affected packages
typo3/cms-coreComposer
- Affected
- >=8.0.0 <8.7.27
- Fixed in
- 8.7.27
Update to the fixed version for your release line, for example:
composer require typo3/cms-core:^8.7.27typo3/cms-coreComposer
- Affected
- >=9.0.0 <9.5.8
- Fixed in
- 9.5.8
Update to the fixed version for your release line, for example:
composer require typo3/cms-core:^9.5.8Details
It has been discovered session data of properly authenticated and logged in frontend users is kept and transformed into an anonymous user session during the logout process. This way the next user using the same client application gains access to previous session data.
Is GHSA-82vp-jr39-4j2j 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-CMS/core/commit/c8c08ca0c26db02753c243e175a8a045628341b6
- Linkgithub.com/TYPO3-CMS/core/commit/fe43834075ae283c8cd91949e9f1dfd18b2d492f
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2019-06-25-3.yaml
- Packagegithub.com/TYPO3-CMS/core
- Linktypo3.org/security/advisory/typo3-core-sa-2019-018
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.