CVE-2012-5216
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 · uneditedCross-site request forgery (CSRF) vulnerability on HP ProCurve 1700-8 (aka J9079A) switches with software before VA.02.09 and 1700-24 (aka J9080A) switches with software before VB.02.09 allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.
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 confidenceCross-site request forgery (CSRF) vulnerability in HP ProCurve 1700-8 (J9079A) and 1700-24 (J9080A) switch web management interfaces allows remote attackers to perform unauthorized actions by tricking authenticated users into submitting malicious requests, hijacking their session authentication.
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<= va.02.08= h= h.07.02= h.07.03= h.07.31= h.07.32= h.07.41= h.07.45= h.07.46= h.07.50= h.07.53= h.07.54all 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 switch console and run 'show system' or 'show version' to display the hardware model. Alternatively, access the web management interface and check the device information page.Affected if The model is HP ProCurve 1700-8 (J9079A) or HP ProCurve 1700-24 (J9080A)
-
Check the software versionRun 'show version' or 'show flash' from the console to display the installed software version. On the web interface, check the system information or firmware version field.Affected if For 1700-8: version is va.02.08 or earlier. For 1700-24: any version. For both: if running any h-series version listed (h.07.02 through h.07.54)
-
Confirm web management interface is enabledRun 'show http' or 'show running-config' to check if the web management interface (http or https) is configured and enabled on the switch.Affected if The web management interface is active and accessible (CSRF requires the web interface to be enabled to be exploitable)
-
Verify the switch is reachable over the networkAttempt to ping the switch IP address or check if ports 80 or 443 are open. From the console, use 'show interface' to confirm IP configuration and status.Affected if The switch has an active IP address and is network accessible (remote exploitation requires network accessibility)
The switch is affected if it is an HP ProCurve 1700-8 or 1700-24 model running a vulnerable software version (va.02.08 or earlier for 1700-8, any version for 1700-24, or any h-series version listed) with the web management interface enabled and network accessible.
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 dataUpdate HP ProCurve 1700-8 switches to software version VA.02.09 or later, and 1700-24 switches to version VB.02.09 or later. Apply within a planned maintenance window following change management procedures.
- Consultation3.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5216 — 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-2012-5216 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