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

> Remote attackers can access sensitive data and gain unauthorized access via undocumented ports on the IP phone without authentication.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-69p9-v7gg-v248

## What is CVE-2006-0374?

CVE-2006-0374 is a high-severity authentication bypass vulnerability in n/a, published on 22 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Advantage Century Telecommunication (ACT) P202S IP Phone 1.01.21 running firmware 1.1.21 has multiple undocumented ports available, which (1) might allow remote attackers to obtain sensitive information, such as memory contents and internal operating-system data, by directly accessing the VxWorks WDB remote debugging ONCRPC (aka wdbrpc) on UDP 17185, (2) reflect network data using echo (TCP 7), or (3) gain access without authentication using rlogin (TCP 513).

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Advantage Century Telecommunication P202s.

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

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

## Is CVE-2006-0374 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0375](https://insights.sbomify.com/CVE-2006-0375/): Hardcoded credentials in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0374 is a high-severity authentication bypass vulnerability in n/a, published on 22 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0374 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-0374/ (Markdown: https://insights.sbomify.com/CVE-2006-0374/index.md)
```

## Sources

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

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