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

> Remote authenticated attackers can reset passwords for users with expired credentials in Cisco Unity Express, leading to account takeover.

- **Severity:** Low 2.1 (`AV:N/AC:H/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6g6q-2h84-3ph5

## What is CVE-2006-2166?

CVE-2006-2166 is a low-severity authentication bypass vulnerability in n/a, published on 4 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the HTTP management interface in Cisco Unity Express (CUE) 2.2(2) and earlier, when running on any CUE Advanced Integration Module (AIM) or Network Module (NM), allows remote authenticated attackers to reset the password for any user with an expired password.

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

It affects 2 products.


Products: Cisco Unity Express, Cisco Unity Express Software.

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

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

## Is CVE-2006-2166 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-15381](https://insights.sbomify.com/CVE-2018-15381/): Cisco Unity Express Arbitrary Command Execution Vulnerability (critical 9.8)
- [CVE-2013-1120](https://insights.sbomify.com/CVE-2013-1120/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2019-15986](https://insights.sbomify.com/CVE-2019-15986/): Cisco Unity Express Command Injection Vulnerability (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2166 is a low-severity authentication bypass vulnerability in n/a, published on 4 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2166 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-2166/ (Markdown: https://insights.sbomify.com/CVE-2006-2166/index.md)
```

## Sources

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

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