CVE-2002-0350
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 · uneditedHP Procurve Switch 4000M running firmware C.08.22 and C.09.09 allows remote attackers to cause a denial of service via a port scan of the management IP address, which disables the telnet service.
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 · moderate confidenceHP Procurve Switch 4000M running firmware versions C.08.22 and C.09.09 contains a denial of service vulnerability where a remote port scan against the management IP address causes the telnet service to become permanently disabled. The switch fails to properly handle certain network traffic patterns during a port scan, resulting in loss of management 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= c.08.22= c.09.09CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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.
-
Confirm the switch modelAccess the switch CLI and run 'show system' or 'show version' to verify the hardware model is HP Procurve Switch 4000MAffected if The model is anything other than HP Procurve Switch 4000M, as this vulnerability is specific to that model only
-
Identify the installed firmware versionRun 'show version' in the switch CLI and locate the firmware version number in the outputAffected if The firmware version is C.08.22 or C.09.09 exactly as listed in the affected versions
-
Check if telnet management is enabledRun 'show telnet' or 'show management' in the switch CLI to see if the telnet service is configured and active for management accessAffected if Telnet management is enabled and the firmware version matches C.08.22 or C.09.09; the vulnerability only affects the telnet service when these specific firmware versions are running
-
Verify management access methodReview switch management configuration to confirm telnet is the primary or secondary access method, noting that SSH or other access methods would not trigger this specific vulnerabilityAffected if Telnet is configured as an active management interface on a switch running affected firmware versions C.08.22 or C.09.09
You are affected if you have an HP Procurve Switch 4000M running firmware version C.08.22 or C.09.09 with telnet management access enabled, as the vulnerability causes permanent telnet denial of service when a port scan is performed against the management IP.
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 dataUpgrade to a newer firmware version if available; if the hardware is end-of-life, replace with a supported switch. Additionally, restrict management access to the switch via network segmentation or ACLs to prevent unauthorized port scans from reaching the management interface.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0350 — 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-0350 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