GHSA-p84g-j2gh-83g3 TYPO3 possible cache poisoning on the homepage when anchors are used
Not scored
Published
Check this codebase for GHSA-p84g-j2gh-83g3 and fix it if it is affected.
What it is: GHSA-p84g-j2gh-83g3 is a vulnerability in typo3/cms, published on 30 May 2024.
Exploitation: There is no known exploitation of GHSA-p84g-j2gh-83g3 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.9
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.9
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.0.2
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.0.2
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-p84g-j2gh-83g3/ (Markdown: https://insights.sbomify.com/GHSA-p84g-j2gh-83g3/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is GHSA-p84g-j2gh-83g3?
GHSA-p84g-j2gh-83g3 is a vulnerability in typo3/cms, published on 30 May 2024.
Official description
A request URL with arbitrary arguments, but still pointing to the home page of a TYPO3 installation can be cached if the configuration option config.prefixLocalAnchors is used with the values "all" or "cached". The impact of this vulnerability is that unfamiliar looking links to the home page can end up in the cache, which leads to a reload of the page in the browser when section links are followed by web page visitors, instead of just directly jumping to the requested section of the page. TYPO3 versions 4.6.x and higher are only affected if the homepage is not a shortcut to a different page.
Which versions are affected by GHSA-p84g-j2gh-83g3?
4 open source packages ship an affected version, including typo3/cms.
| Package | Affected | Fixed in |
|---|---|---|
typo3/cms Packagist | From 6.2.0 | 6.2.9 |
typo3/cms Packagist | From 6.2.0 | 6.2.9 |
typo3/cms Packagist | From 7.0.0 | 7.0.2 |
typo3/cms Packagist | From 7.0.0 | 7.0.2 |
How do I fix GHSA-p84g-j2gh-83g3?
Upgrade typo3/cms to a fixed version for your release line: 6.2.9 or 7.0.2.
Is GHSA-p84g-j2gh-83g3 being exploited?
There is no known exploitation of GHSA-p84g-j2gh-83g3 in the wild and no public exploit code.