# CVE-2006-3360: phpSysInfo allows remote attackers to determine the existence of arbitrary files via a .. (dot dot) sequence

> Remote attackers can determine the existence of arbitrary files on the server via directory traversal in the lng parameter.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-3360, GHSA-2wxv-3g4v-p76p

## What is CVE-2006-3360?

CVE-2006-3360 is a medium-severity path traversal vulnerability in n/a, published on 6 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in index.php in phpSysInfo 2.5.1 allows remote attackers to determine the existence of arbitrary files via a .. (dot dot) sequence and a trailing null (%00) byte in the lng parameter, which will display a different error message if the file exists.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2006-3360?

2 open source packages ship an affected version, including phpsysinfo/phpsysinfo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `phpsysinfo/phpsysinfo` | Packagist | All versions | 3.2.5 |
| `phpsysinfo/phpsysinfo` | Packagist | All versions | 3.2.5 |

Products: Phpsysinfo Phpsysinfo.

## How do I fix CVE-2006-3360?

Upgrade phpsysinfo/phpsysinfo to 3.2.5 or later.

## Is CVE-2006-3360 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-49006](https://insights.sbomify.com/CVE-2023-49006/): Phpsysinfo Cross Site Request Forgery (CSRF) vulnerability (medium 6.5)
- [CVE-2005-0869](https://insights.sbomify.com/CVE-2005-0869/): Information disclosure in n/a (medium 5.0)
- [CVE-2007-4048](https://insights.sbomify.com/CVE-2007-4048/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2005-3348](https://insights.sbomify.com/CVE-2005-3348/): Other in n/a (medium 4.3)
- [CVE-2005-0870](https://insights.sbomify.com/CVE-2005-0870/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-3360 and fix it if it is affected.

What it is: CVE-2006-3360 is a medium-severity path traversal vulnerability in n/a, published on 6 Jul 2006. 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-2006-3360 in the wild and no public exploit code.

Affected packages and fixed versions:
- phpsysinfo/phpsysinfo (Packagist): affected all versions; fixed in 3.2.5
- phpsysinfo/phpsysinfo (Packagist): affected all versions; fixed in 3.2.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-2006-3360/ (Markdown: https://insights.sbomify.com/CVE-2006-3360/index.md)
```

## Sources

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

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