# CVE-2005-0506: Information disclosure in n/a

> Local attackers can steal cleartext credentials from the Windows registry to impersonate users in Avaya IP Office Phone Manager.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9337-pphj-26cr

## What is CVE-2005-0506?

CVE-2005-0506 is a medium-severity vulnerability in n/a, published on 22 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Avaya IP Office Phone Manager, and other products such as the IP Softphone, stores sensitive data in cleartext in a registry key, which allows local and possibly remote users to steal usernames and passwords and impersonate other users via keys such as Avaya\IP400\Generic.

## Which versions are affected by CVE-2005-0506?

It affects 2 products.


Products: Avaya Ip Office Phone Manager, Avaya Ip Soft Phone.

## How do I fix CVE-2005-0506?

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

## Is CVE-2005-0506 being exploited?

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

Public exploit code:

- Avaya IP Office Phone Manager - Local Password Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0506 and fix it if it is affected.

What it is: CVE-2005-0506 is a medium-severity vulnerability in n/a, published on 22 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0506 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-2005-0506/ (Markdown: https://insights.sbomify.com/CVE-2005-0506/index.md)
```

## Sources

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

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