dbcve.org
Procurve Switch SoftwareOperating system · Hp

CVE-2010-2705

MEDIUM · 6.1 CVSS v2.0 Published 2010-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Unspecified vulnerability on the HP ProCurve 1800-24G switch with software PB.03.02 and earlier, and the ProCurve 1800-8G switch with software PA.03.02 and earlier, when SNMP is enabled, allows remote attackers to obtain sensitive information 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 confidence

Unspecified vulnerability in HP ProCurve 1800-24G (PB.03.02 and earlier) and 1800-8G (PA.03.02 and earlier) switches allows remote attackers to obtain sensitive information when SNMP is enabled. The exact exploitation vector is unknown but the attack is network-accessible.

MitigationDisable SNMP if not required for network management, or upgrade switch firmware beyond PB.03.02 (1800-24G) and PA.03.02 (1800-8G) to remediate the vulnerability.

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
Procurve Switch SoftwareOperating system
Affected:<= pb.03.02= pb.02.01= pb.02.02= pb.02.03= pb.02.04= pb.02.05= pb.02.06= pb.02.07= pb.02.08= pb.02.09= pb.03.00= pb.03.01
Procurve Switch 1800 24gHardware / appliance
Affected:all versions
Procurve Switch 1800 8gHardware / appliance
Affected:all versions

CVSS 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
Complete
Integrity
None
Availability
None

AV:A/AC:L/Au:N/C:C/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the switch model
    Check the physical device label, web interface, or console output to confirm the model is HP ProCurve 1800-24G or 1800-8G
    Affected if Device is an HP ProCurve 1800-24G or 1800-8G switch
  2. Determine the firmware version
    Access the switch web interface, console, or use SNMP GET on OID 1.3.6.1.2.1.1.1.0 to retrieve the firmware version string
    Affected if Firmware version is PB.03.02 or earlier for 1800-24G, or PA.03.02 or earlier for 1800-8G
  3. Verify if SNMP is enabled
    Check SNMP configuration via the switch web interface under SNMP settings, console CLI command 'show snmp-server', or query SNMP UDP port 161
    Affected if SNMP is enabled on the switch

The environment is affected if the switch is an HP ProCurve 1800-24G or 1800-8G running firmware at or below PB.03.02 (24G) or PA.03.02 (8G) with SNMP enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable SNMP if not required for network management, or upgrade switch firmware beyond PB.03.02 (1800-24G) and PA.03.02 (1800-8G) to remediate the vulnerability.

Fix this in Procurve Switch Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-2705 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-2705 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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