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

> Local attackers can bypass authentication via UPnP to access protected files on Siemens Speedstream routers.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w29p-ghvg-3jxf

## What is CVE-2006-3344?

CVE-2006-3344 is a high-severity authentication bypass vulnerability in n/a, published on 3 Jul 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Siemens Speedstream Wireless Router 2624 allows local users to bypass authentication and access protected files by using the Universal Plug and Play UPnP/1.0 component.

Weakness: CWE-264

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

It affects 1 product.


Products: Siemens Speedstream Wireless Router.

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

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

## Is CVE-2006-3344 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3907](https://insights.sbomify.com/CVE-2006-3907/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3344 is a high-severity authentication bypass vulnerability in n/a, published on 3 Jul 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-3344 in the wild and no public exploit code.

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

## Sources

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

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