# CVE-2010-3287: Other in n/a

> Remote attackers can execute arbitrary code on HP ProCurve wireless infrastructure devices via unspecified vectors.

- **Severity:** High 8.3 (`AV:A/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g79r-j452-v9g3

## What is CVE-2010-3287?

CVE-2010-3287 is a high-severity vulnerability in n/a, published on 18 Oct 2010. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified 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.

## Which versions are affected by CVE-2010-3287?

It affects 18 products.


Products: Hp Procurve Access Point Software, Hp Procurve M110 Access Point, Hp Procurve Miltope Dual Radio Access Point, Hp Procurve Msm310-R Access Point, Hp Procurve Msm310 Access Point, Hp Procurve Msm320-R Access Point, Hp Procurve Msm320 Access Point, Hp Procurve Msm325 Access Point, Hp Procurve Msm335 Access Point, Hp Procurve Msm410 Access Point, Hp Procurve Msm422 Access Point, Hp Procurve Msm710 Access Controller, Hp Procurve Msm710 Mobility Controller, Hp Procurve Msm730 Access Controller, Hp Procurve Msm730 Mobility Controller, Hp Procurve Msm750 Access Controller, Hp Procurve Msm750 Mobility Controller, Hp Procurve Multi Service Access Point Miltope Nmap.

## How do I fix CVE-2010-3287?

No fix has been published for CVE-2010-3287 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-3287 being exploited?

There is no known exploitation of CVE-2010-3287 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3287 and fix it if it is affected.

What it is: CVE-2010-3287 is a high-severity vulnerability in n/a, published on 18 Oct 2010. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-3287 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-3287/ (Markdown: https://insights.sbomify.com/CVE-2010-3287/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-3287
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-3287
- OSV: https://osv.dev/vulnerability/CVE-2010-3287

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-3287/
Summaries are generated and may contain mistakes; the official description above is the record.