GHSA-82vp-jr39-4j2j TYPO3 Security Misconfiguration in Frontend Session Handling
Not scored
Published
Check this codebase for GHSA-82vp-jr39-4j2j and fix it if it is affected.
What it is: GHSA-82vp-jr39-4j2j is a vulnerability in typo3/cms-core, published on 30 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-82vp-jr39-4j2j in the wild and no public exploit code.
Affected packages and fixed versions:
- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.27
- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.27
- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.8
- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.8
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/GHSA-82vp-jr39-4j2j/ (Markdown: https://insights.sbomify.com/GHSA-82vp-jr39-4j2j/index.md)
Authenticated frontend users' session data is exposed to subsequent anonymous users due to improper session handling during logout.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is GHSA-82vp-jr39-4j2j?
GHSA-82vp-jr39-4j2j is a vulnerability in typo3/cms-core, published on 30 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
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.
Which versions are affected by GHSA-82vp-jr39-4j2j?
4 open source packages ship an affected version, including typo3/cms-core.
| Package | Affected | Fixed in |
|---|---|---|
typo3/cms-core Packagist | From 8.0.0 | 8.7.27 |
typo3/cms-core Packagist | From 8.0.0 | 8.7.27 |
typo3/cms-core Packagist | From 9.0.0 | 9.5.8 |
typo3/cms-core Packagist | From 9.0.0 | 9.5.8 |
How do I fix GHSA-82vp-jr39-4j2j?
Upgrade typo3/cms-core to a fixed version for your release line: 8.7.27 or 9.5.8.
Is GHSA-82vp-jr39-4j2j being exploited?
There is no known exploitation of GHSA-82vp-jr39-4j2j in the wild and no public exploit code.