CVE-2010-3287
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 on HP ProCurve Access Points, Access Controllers, and Mobility Controllers with software 5.1.x through 5.1.9, 5.2.x through 5.2.7, 5.3.x through 5.3.5, and 5.4.x through 5.4.0 allows remote attackers to execute arbitrary code 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 confidenceThis is an unspecified vulnerability in HP ProCurve wireless infrastructure devices (Access Points, Access Controllers, and Mobility Controllers) affecting software versions 5.1.x through 5.1.9, 5.2.x through 5.2.7, 5.3.x through 5.3.5, and 5.4.x through 5.4.0. The flaw allows remote attackers to execute arbitrary code without authentication, likely through a network-based attack vector.
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= 5.1.0= 5.1.2= 5.1.3= 5.1.4= 5.1.6= 5.1.7= 5.1.8= 5.1.9= 5.2.0= 5.2.1= 5.2.2= 5.2.4all versionsall 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:L/Au:N/C:C/I:C/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 device modelDetermine if the device is an HP ProCurve wireless Access Point, Access Controller, or Mobility Controller. Check the physical device label, web interface, or CLI output for the exact model name (e.g., M110, MSM310, MSM320, MSM325).Affected if The device is any HP ProCurve Access Point, Access Controller, or Mobility Controller model listed in the affected products.
-
Check software version for specific range modelsAccess the device management interface (web UI or CLI) and locate the software/firmware version information. For Access Point Software models with version ranges (5.1.x through 5.1.9, 5.2.x through 5.2.7, 5.3.x through 5.3.5, 5.4.x through 5.4.0), compare your installed version against these ranges.Affected if The installed software version falls within 5.1.0-5.1.9, 5.2.0-5.2.7, 5.3.0-5.3.5, or 5.4.0-5.4.0.
-
Check version for 'all versions' modelsFor HP ProCurve M110, Miltope Dual Radio, MSM310, MSM320, and MSM325 Access Points, check any installed software version regardless of number.Affected if Any software version is installed on these models (they are all affected).
-
Verify management interface exposureExamine network configuration to determine if the device management interface (web UI, CLI, or SNMP) is accessible from untrusted networks or the public internet.Affected if Management interface is exposed to untrusted networks (this vulnerability is exploitable via network-based attack vector).
The environment is affected if any HP ProCurve wireless device (Access Point, Access Controller, or Mobility Controller) is running a software version within 5.1.x-5.1.9, 5.2.x-5.2.7, 5.3.x-5.3.5, or 5.4.x-5.4.0, or if the device is an M110, Miltope Dual Radio, MSM310, MSM320, or MSM325 model with any version.
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 affected HP ProCurve devices to a vendor-patched software version beyond 5.4.0. As a temporary control, restrict network access to management interfaces and implement network segmentation to limit exposure to untrusted networks.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3287 — 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-3287 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