GHSA-c7rj-92xr-wprg Insecure Unserialize in TYPO3 Backend
Not scored
Published
Check this codebase for GHSA-c7rj-92xr-wprg and fix it if it is affected.
What it is: GHSA-c7rj-92xr-wprg is an unsafe deserialization vulnerability in typo3/cms, published on 5 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-c7rj-92xr-wprg 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.29
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.29
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.13
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.13
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.4.1
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.4.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-c7rj-92xr-wprg/ (Markdown: https://insights.sbomify.com/GHSA-c7rj-92xr-wprg/index.md)
An authenticated backend user can exploit insecure deserialization in the suggest wizard to execute arbitrary code.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-c7rj-92xr-wprg?
GHSA-c7rj-92xr-wprg is an unsafe deserialization vulnerability in typo3/cms, published on 5 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Failing to properly validate incoming data, the suggest wizard is susceptible to insecure unserialize. To exploit this vulnerability a valid backend user account is needed.
Which versions are affected by GHSA-c7rj-92xr-wprg?
6 open source packages ship an affected version, including typo3/cms.
| Package | Affected | Fixed in |
|---|---|---|
typo3/cms Packagist | From 6.2.0 | 6.2.29 |
typo3/cms Packagist | From 6.2.0 | 6.2.29 |
typo3/cms Packagist | From 7.6.0 | 7.6.13 |
typo3/cms Packagist | From 7.6.0 | 7.6.13 |
typo3/cms Packagist | From 8.0.0 | 8.4.1 |
typo3/cms Packagist | From 8.0.0 | 8.4.1 |
How do I fix GHSA-c7rj-92xr-wprg?
Upgrade typo3/cms to a fixed version for your release line: 6.2.29, 7.6.13 or 8.4.1.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is GHSA-c7rj-92xr-wprg being exploited?
There is no known exploitation of GHSA-c7rj-92xr-wprg in the wild and no public exploit code.