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

> Remote attackers can read arbitrary files, including configuration files, from the ECI Telecom B-FOCuS router via a specific HTTP request.

- **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-2v33-cf4x-5rqf

## What is CVE-2006-5711?

CVE-2006-5711 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

ECI Telecom B-FOCuS Wireless 802.11b/g ADSL2+ Router allows remote attackers to read arbitrary files via a certain HTTP request, as demonstrated by a request for a router configuration file, related to the /html/defs/ URI.

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

It affects 1 product.


Products: Eci Telecom B-Focus Wireless 802.11bg Adsl2\+ Router.

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

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

## Is CVE-2006-5711 being exploited?

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

Public exploit code:

- ECI Telecom B-Focus ADSL2+ Combo332+ Wireless Router - Information Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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