GHSA-r9vc-jfmh-6j48 json
TYPO3 frontend login vulnerable to Session Fixation
published 2y ago modified last yr.
- cvss
- 7.1
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist typo3/cms 6.2.14, 7.3.1
- github.com/TYPO3/typo3@4c9aba9 commit
- github.com/TYPO3/typo3@4f6e84b commit
Is GHSA-r9vc-jfmh-6j48 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms | >=6.2.0, <6.2.14 >=7.0.0, <7.3.1 |
6.2.14 7.3.1 |
Classification
- Weakness
-
- CWE-384 Session Fixation
References
-
github.com
/TYPO3/typo3/commit/4c9aba94a930d56ab374693c9c5cc0458587278a
web
-
github.com
/TYPO3/typo3/commit/4f6e84bba3c13ea8b2652af1a4c47758aa0705f4
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2015-07-01-2.yaml
web
-
github.com
/TYPO3/typo3
package
-
typo3.org
/security/advisory/typo3-core-sa-2015-003
web
-
typo3.org
/teams/security/security-bulletins/typo3-core/typo3-core-sa-2015-003
web
Sources
- GitHub Advisory GHSA-r9vc-jfmh-6j48
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.