# CVE-2006-4140: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in IPCheck Server Monitor, exposing sensitive data.

- **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:** No
- **Published:** 14 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mw52-hqx9-7696

## What is CVE-2006-4140?

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

### Official description

Directory traversal vulnerability in IPCheck Server Monitor before 5.3.3.639/640 allows remote attackers to read arbitrary files via modified .. (dot dot) sequences in the URL, including (1) "..%2f" (encoded "/" slash), "..../" (multiple dot), and "..%255c../" (double-encoded "\" backslash).

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

It affects 1 product.


Products: Ipcheck Server Monitor.

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

No fix has been published for CVE-2006-4140 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-4140 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4140 exists.

Public exploit code:

- IPCheck Server Monitor 5.x - Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4140 is a medium-severity path traversal vulnerability in n/a, published on 14 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4140 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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