GHSA-vpr3-rc99-2wpr Information Disclosure in TYPO3 Backend
Not scored
Published
Check this codebase for GHSA-vpr3-rc99-2wpr and fix it if it is affected.
What it is: GHSA-vpr3-rc99-2wpr is a vulnerability in typo3/cms, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-vpr3-rc99-2wpr in the wild and no public exploit code.
Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.26
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.26
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.10
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.10
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.2.1
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.2.1
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-vpr3-rc99-2wpr/ (Markdown: https://insights.sbomify.com/GHSA-vpr3-rc99-2wpr/index.md)
Attackers can guess cache file paths to retrieve valid backend usernames, exposing sensitive authentication data.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-vpr3-rc99-2wpr?
GHSA-vpr3-rc99-2wpr is a vulnerability in typo3/cms, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The TYPO3 backend module stores the username of an authenticated backend user in its cache files. By guessing the file path to the cache files it is possible to receive valid backend usernames.
Which versions are affected by GHSA-vpr3-rc99-2wpr?
6 open source packages ship an affected version, including typo3/cms.
| Package | Affected | Fixed in |
|---|---|---|
typo3/cms Packagist | From 6.2.0 | 6.2.26 |
typo3/cms Packagist | From 6.2.0 | 6.2.26 |
typo3/cms Packagist | From 7.6.0 | 7.6.10 |
typo3/cms Packagist | From 7.6.0 | 7.6.10 |
typo3/cms Packagist | From 8.0.0 | 8.2.1 |
typo3/cms Packagist | From 8.0.0 | 8.2.1 |
How do I fix GHSA-vpr3-rc99-2wpr?
Upgrade typo3/cms to a fixed version for your release line: 6.2.26, 7.6.10 or 8.2.1.
Is GHSA-vpr3-rc99-2wpr being exploited?
There is no known exploitation of GHSA-vpr3-rc99-2wpr in the wild and no public exploit code.