CVE-2002-1229
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 · uneditedAvaya Cajun switches P880, P882, P580, and P550R 5.2.14 and earlier contain undocumented accounts (1) manuf and (2) diag with default passwords, which allows remote attackers to gain privileges.
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 Cajun switches (P880, P882, P580, P550R) firmware 5.2.14 and earlier contain two undocumented hardcoded accounts ('manuf' and 'diag') with default passwords, allowing remote unauthenticated attackers to gain full administrative privileges via Telnet or other remote access.
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 data= 4.3.5= 5.2.14= 5.2.14= 5.2.14= 5.2.14CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 the switch modelLog into the device or check its management interface to confirm the exact model number (P550, P550r, P580, P880, or P882). This vulnerability only affects these specific Avaya Cajun switch models.Affected if The device is any of: P550, P550r, P580, P880, or P882.
-
Check the firmware versionUse the command 'show version' or 'show system' via console or management interface to retrieve the running firmware version. Compare it against the affected ranges: P550 = 4.3.5 and below; P550r/P580/P880/P882 = 5.2.14 and below.Affected if The firmware version is 4.3.5 or lower on P550, or 5.2.14 or lower on P550r/P580/P880/P882.
-
Verify if Telnet access is enabledCheck the switch configuration using 'show running-config' or review the management access settings. Look for 'telnet' or port 23 in the access configuration.Affected if Telnet (port 23) or other remote management protocols are enabled and accessible from untrusted networks.
-
Confirm remote administrative access is exposedReview ACLs, VLAN settings, and management interface bindings. Determine if the switch management IP is reachable from outside trusted networks.Affected if The switch administrative interface is reachable from networks that are not explicitly trusted.
You are affected if you run an Avaya Cajun P550 (firmware <=4.3.5) or P550r/P580/P880/P882 (firmware <=5.2.14) with Telnet or remote management access enabled, as the undocumented 'manuf' and 'diag' accounts become exploitable via that attack surface.
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 dataDisable or change passwords on undocumented accounts 'manuf' and 'diag' if possible, upgrade firmware to version beyond 5.2.14, and restrict management interface access to trusted networks to prevent remote exploitation.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1229 — 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-2002-1229 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