CVE-2010-2706
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 · uneditedUnspecified vulnerability in the In-band Agent on the HP ProCurve 2610 switch before R.11.30 allows remote attackers to cause a denial of service 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 · moderate confidenceA denial of service vulnerability exists in the In-band Agent component of HP ProCurve 2610 switches running firmware versions prior to R.11.30. Remote attackers can exploit unknown vectors to cause the switch to become unavailable, disrupting network connectivity.
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<= r.11.29= r.11.04= r.11.05= r.11.06= r.11.07= r.11.08= r.11.09= r.11.10= r.11.11= r.11.12= r.11.13= r.11.14all versionsall versionsall versionsall versionsall 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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:A/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.
-
Identify the HP ProCurve switch modelLog into the switch CLI and run 'show system' or check the physical label to confirm it is an HP ProCurve 2610, 2610-24, 2610-24-Pwr, 2610-24/12pwr, 2610-48, or 2610-48-Pwr modelAffected if The switch is not an HP ProCurve 2610 series model - if it is a different model, this specific CVE does not apply
-
Check the installed firmware versionLog into the switch CLI and run 'show version' to display the firmware version information. Look for the software version number (for example, R.11.26, R.11.29, etc.)Affected if The firmware version is R.11.29 or earlier, or specifically R.11.04 through R.11.14 as listed in the affected versions. Versions prior to R.11.30 are vulnerable.
-
Verify In-band Agent statusLog into the switch CLI and run 'show running-config' or 'show management' to check if the In-band Agent feature is enabled. Look for configuration lines related to in-band management or In-band AgentAffected if In-band Agent is enabled. The vulnerability exploits this component, so if it is disabled the exploit vector may not be accessible
You are affected if you have an HP ProCurve 2610 series switch running firmware version R.11.29 or earlier (including R.11.04 through R.11.14) with In-band Agent enabled, as this combination allows remote attackers to cause denial of service via the In-band Agent component.
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 the HP ProCurve 2610 switch firmware to version R.11.30 or later to address this vulnerability. Ensure proper backup of switch configuration before upgrading.
- Consultation3.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2706 — 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-2010-2706 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