CVE-2002-1147
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 HTTP administration interface for HP Procurve 4000M Switch firmware before C.09.16, with stacking features and remote administration enabled, does not authenticate requests to reset the device, which allows remote attackers to cause a denial of service via a direct request to the device_reset CGI program.
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 confidenceThe HTTP administration interface in HP Procurve 4000M switches with remote administration enabled lacks authentication on the device_reset CGI program, allowing unauthenticated remote attackers to reset the device and cause denial of service.
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.09.15CVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/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 device modelAccess the switch web interface or CLI and identify the exact model. In the web interface, this is typically visible on the main status page. Via CLI, use 'show system-information' or similar command.Affected if The device is not an HP Procurve Switch 4000M, then this specific CVE does not apply.
-
Check firmware versionIn the web interface, navigate to the Administration or Management section to view the firmware version. Via CLI, use 'show version' or 'show flash' to see installed firmware.Affected if The firmware version is c.09.15 or lower (any version <= c.09.15), placing it within the affected range.
-
Verify remote HTTP administration statusIn the web interface, go to Configuration > Remote Management or Administration > HTTP Remote Management settings. Via CLI, check the HTTP server configuration with 'show http-server' or similar.Affected if Remote HTTP administration is enabled, making the device accessible over HTTP for remote management and exposing the vulnerable CGI program.
-
Confirm device_reset CGI accessibilityAttempt to access the device_reset CGI program via HTTP: http://<device_ip>/device_reset or check the web interface CGIbin directory for available programs.Affected if The CGI program is accessible without authentication, confirming the vulnerability is present and exploitable.
A user is affected if they have an HP Procurve Switch 4000M with firmware version c.09.15 or lower AND remote HTTP administration is enabled, allowing unauthenticated access to the device_reset CGI program.
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 firmware C.09.16 or later to remediate this vulnerability; alternatively, disable remote HTTP administration if not required.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1147 — 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-1147 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