# CVE-2006-3561: Auth bypass in n/a

> Remote attackers can bypass authentication to access sensitive configuration and PPP credentials on BT Voyager 2091 routers.

- **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:** 13 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5gpw-gj4x-9w63

## What is CVE-2006-3561?

CVE-2006-3561 is a medium-severity authentication bypass vulnerability in n/a, published on 13 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BT Voyager 2091 Wireless firmware 2.21.05.08m_A2pB018c1.d16d and earlier, and 3.01m and earlier, allow remote attackers to bypass the authentication process and gain sensitive information, such as configuration information via (1) /btvoyager_getconfig.sh, PPP credentials via (2) btvoyager_getpppcreds.sh, and decode configuration credentials via (3) btvoyager_decoder.c.

Weakness: CWE-264, CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Bt Voyager 2091 Wireless Adsl Router.

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

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

## Is CVE-2006-3561 being exploited?

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

Public exploit code:

- BT Voyager 2091 (Wireless ADSL) - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3561 is a medium-severity authentication bypass vulnerability in n/a, published on 13 Jul 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-3561 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-3561/ (Markdown: https://insights.sbomify.com/CVE-2006-3561/index.md)
```

## Sources

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

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