GHSA-82vp-jr39-4j2j json
TYPO3 Security Misconfiguration in Frontend Session Handling
published 2y ago modified last yr.
- cvss
- 8.2
- 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 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.
Patch / fix
- packagist typo3/cms-core 8.7.27, 9.5.8
Is GHSA-82vp-jr39-4j2j 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 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms-core | >=8.0.0, <8.7.27 >=9.0.0, <9.5.8 |
8.7.27 9.5.8 |
Classification
- Weakness
-
- CWE-488 Exposure of Data Element to Wrong Session
References
-
github.com
/TYPO3-CMS/core/commit/c8c08ca0c26db02753c243e175a8a045628341b6
web
-
github.com
/TYPO3-CMS/core/commit/fe43834075ae283c8cd91949e9f1dfd18b2d492f
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2019-06-25-3.yaml
web
-
github.com
/TYPO3-CMS/core
package
-
typo3.org
/security/advisory/typo3-core-sa-2019-018
web
Sources
- GitHub Advisory GHSA-82vp-jr39-4j2j
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.