# CVE-2010-5099: TYPO3 Path Traversal vulnerability

> Remote attackers can bypass file inclusion protections to read arbitrary PHP files, including sensitive configuration data, via path traversal.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 May 2012
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2012-2344, GHSA-66j3-66cp-6c2m

## What is CVE-2010-5099?

CVE-2010-5099 is a medium-severity path traversal vulnerability in Typo3 Typo3, published on 30 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The fileDenyPattern functionality in the PHP file inclusion protection API in TYPO3 4.2.x before 4.2.16, 4.3.x before 4.3.9, and 4.4.x before 4.4.5 does not properly filter file types, which allows remote attackers to bypass intended access restrictions and access arbitrary PHP files, as demonstrated using path traversal sequences with %00 null bytes and CVE-2010-3714 to read the TYPO3 encryption key from localconf.php.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2010-5099?

6 open source packages ship an affected version, including typo3/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 4.2.0 | 4.2.16 |
| `typo3/cms` | Packagist | From 4.2.0 | 4.2.16 |
| `typo3/cms` | Packagist | From 4.3.0 | 4.3.9 |
| `typo3/cms` | Packagist | From 4.3.0 | 4.3.9 |
| `typo3/cms` | Packagist | From 4.4.0 | 4.4.5 |
| `typo3/cms` | Packagist | From 4.4.0 | 4.4.5 |

Products: Typo3 Typo3.

## How do I fix CVE-2010-5099?

Upgrade typo3/cms to a fixed version for your release line: 4.2.16, 4.3.9 or 4.4.5.

## Is CVE-2010-5099 being exploited?

There is no known exploitation of CVE-2010-5099 in the wild and no public exploit code.

Public exploit code:

- TYPO3 - Arbitrary File Retrieval (exploitdb)

## Other vulnerabilities in Typo3 Typo3

- [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0)
- [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8)
- [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8)
- [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8)
- [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-5099 and fix it if it is affected.

What it is: CVE-2010-5099 is a medium-severity path traversal vulnerability in Typo3 Typo3, published on 30 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-5099 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 4.2.0; fixed in 4.2.16
- typo3/cms (Packagist): affected from 4.2.0; fixed in 4.2.16
- typo3/cms (Packagist): affected from 4.3.0; fixed in 4.3.9
- typo3/cms (Packagist): affected from 4.3.0; fixed in 4.3.9
- typo3/cms (Packagist): affected from 4.4.0; fixed in 4.4.5
- typo3/cms (Packagist): affected from 4.4.0; fixed in 4.4.5

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-2010-5099/ (Markdown: https://insights.sbomify.com/CVE-2010-5099/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-5099
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-5099
- OSV: https://osv.dev/vulnerability/CVE-2010-5099

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-5099/
Summaries are generated and may contain mistakes; the official description above is the record.