CVE-2011-4627 Typo3 Information Disclosure
Medium 6.5
Published
Updated
Check this codebase for CVE-2011-4627 and fix it if it is affected.
What it is: CVE-2011-4627 is a medium-severity vulnerability in Typo3 Typo3, published on 6 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4627 in the wild and no public exploit code.
Affected packages and fixed versions:
- typo3/cms (Packagist): affected all versions; fixed in 4.3.12
- typo3/cms (Packagist): affected all versions; fixed in 4.3.12
- typo3/cms (Packagist): affected from 4.4.0; fixed in 4.4.9
- typo3/cms (Packagist): affected from 4.4.0; fixed in 4.4.9
- typo3/cms (Packagist): affected from 4.5.0; fixed in 4.5.4
- typo3/cms (Packagist): affected from 4.5.0; fixed in 4.5.4
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/CVE-2011-4627/ (Markdown: https://insights.sbomify.com/CVE-2011-4627/index.md)
An information disclosure vulnerability in the TYPO3 backend allows attackers to access sensitive data.
- 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 CVE-2011-4627?
CVE-2011-4627 is a medium-severity vulnerability in Typo3 Typo3, published on 6 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
TYPO3 before 4.3.12, 4.4.x before 4.4.9, and 4.5.x before 4.5.4 allows Information Disclosure on the backend.
Weakness: CWE-200
Which versions are affected by CVE-2011-4627?
6 open source packages ship an affected version, including typo3/cms. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
typo3/cms Packagist | All versions | 4.3.12 |
typo3/cms Packagist | All versions | 4.3.12 |
typo3/cms Packagist | From 4.4.0 | 4.4.9 |
typo3/cms Packagist | From 4.4.0 | 4.4.9 |
typo3/cms Packagist | From 4.5.0 | 4.5.4 |
typo3/cms Packagist | From 4.5.0 | 4.5.4 |
Products include Typo3 Typo3.
How do I fix CVE-2011-4627?
Upgrade typo3/cms to a fixed version for your release line: 4.3.12, 4.4.9 or 4.5.4.
Is CVE-2011-4627 being exploited?
There is no known exploitation of CVE-2011-4627 in the wild and no public exploit code.
Other vulnerabilities in Typo3 Typo3
- CVE-2009-0258 Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection
- CVE-2011-3583 Typo3 SQL injection due to faulty prepared statements
- CVE-2011-4628 Typo3 Authentication Bypass
- CVE-2023-24814 Persisted Cross-Site Scripting in Frontend Rendering in typo3
- CVE-2021-41113 Cross-Site-Request-Forgery in Backend URI Handling in Typo3
Sources
Also known as GHSA-frf4-5p2c-c3ff.