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

> Remote attackers can read arbitrary files under the web root by exploiting NTFS alternate data streams in Easy Address Book.

- **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:** 4 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f659-ghf2-mmjx

## What is CVE-2006-5715?

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

### Official description

Easy File Sharing (EFS) Easy Address Book 1.2, when run on an NTFS file system, allows remote attackers to read arbitrary files under the web root by appending "::$DATA" to the end of an HTTP GET request, which accesses the alternate data stream.

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

It affects 1 product.


Products: Efs Software Easy Address Book.

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

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

## Is CVE-2006-5715 being exploited?

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

Public exploit code:

- EFS Easy Address Book Web Server 1.2 - Remote File Stream (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5715 is a medium-severity path traversal vulnerability in n/a, published on 4 Nov 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-5715 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-5715/ (Markdown: https://insights.sbomify.com/CVE-2006-5715/index.md)
```

## Sources

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

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