CVE-2005-0506
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAvaya IP Office Phone Manager and IP Softphone store usernames and passwords in cleartext within Windows registry keys under paths such as Avaya\IP400\Generic, allowing local users with registry access to read plaintext credentials and impersonate other users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Avaya IP Office productsCheck Programs and Features or look for Avaya IP Office Phone Manager or IP Softphone in the system. Also check registry key HKLM\SOFTWARE\Avaya\IP400 or search for Avaya in the registry.Affected if Either Avaya IP Office Phone Manager or IP Softphone is installed on the system.
-
Locate the registry key storing credentialsOpen regedit and navigate to the path HKLM\SOFTWARE\Avaya\IP400\Generic or search for subkeys under HKLM\SOFTWARE\Avaya\IP400 that contain username or password values.Affected if The registry path Avaya\IP400\Generic or related IP400 subkeys exist on the system.
-
Inspect stored credential valuesExamine the values in the identified registry keys. Look for data fields named username, password, user, pass, or similar that contain credential information.Affected if Username and password values are present in the registry under the Avaya IP400 keys.
-
Verify credentials are stored in plaintextCheck if the password value contains readable text rather than encoded, encrypted, or hashed characters. Plaintext passwords will appear as clear, human-readable strings.Affected if The password field in the registry contains plaintext (unencrypted) credentials that can be read directly.
A system is affected if Avaya IP Office Phone Manager or IP Softphone is installed and the registry under Avaya\IP400\Generic contains readable plaintext passwords.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict registry key permissions to prevent unauthorized access, and contact Avaya for patches that implement encrypted credential storage rather than plaintext storage.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-0506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-0506 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data