# CVE-2006-0834: Hardcoded credentials in n/a

> Remote attackers can access sensitive device information and connect to other hosts using the default admin password.

- **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 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p935-279c-cj4c

## What is CVE-2006-0834?

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

### Official description

Uniden UIP1868P VoIP Telephone and Router has a default password of admin for the web-based configuration utility, which allows remote attackers to obtain sensitive information on the device such as telephone numbers called, and possibly connect to other hosts.  NOTE: it is possible that this password was configured by a reseller, not the original vendor; if so, then this is not a vulnerability in the product.

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

It affects 1 product.


Products: Uniden Uip1868p.

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

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

## Is CVE-2006-0834 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0834 is a high-severity vulnerability in n/a, published on 22 Feb 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-0834 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-0834/ (Markdown: https://insights.sbomify.com/CVE-2006-0834/index.md)
```

## Sources

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

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