HighGHSA-r9vc-jfmh-6j48
TYPO3 frontend login vulnerable to Session Fixation
Published 30 May 2024 · Updated 5 Dec 2024
Affected packages
typo3/cmsComposer
- Affected
- >=6.2.0 <6.2.14
- Fixed in
- 6.2.14
Update to the fixed version for your release line, for example:
composer require typo3/cms:^6.2.14typo3/cmsComposer
- Affected
- >=7.0.0 <7.3.1
- Fixed in
- 7.3.1
Update to the fixed version for your release line, for example:
composer require typo3/cms:^7.3.1Details
It has been discovered that TYPO3 is susceptible to session fixation. If a user authenticates while anonymous session data is present, the session id is not changed. This makes it possible for attackers to generate a valid session id, trick users into using this session id (e.g. by leveraging a different Cross-Site Scripting vulnerability) and then maybe getting access to an authenticated session.
Is GHSA-r9vc-jfmh-6j48 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, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/typo3/commit/4c9aba94a930d56ab374693c9c5cc0458587278a
- Linkgithub.com/TYPO3/typo3/commit/4f6e84bba3c13ea8b2652af1a4c47758aa0705f4
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2015-07-01-2.yaml
- Packagegithub.com/TYPO3/typo3
- Linktypo3.org/security/advisory/typo3-core-sa-2015-003
- Linktypo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2015-003
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.