# CVE-2010-0104: Code injection in n/a

> Remote attackers can execute arbitrary code on HP Small Form Factor and Microtower platforms via Broadcom NIC firmware vulnerabilities.

- **Severity:** Critical 10.0 (`AV:N/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 Mar 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hxjg-cjpx-x3x5

## What is CVE-2010-0104?

CVE-2010-0104 is a critical code injection vulnerability in n/a, published on 18 Mar 2010. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Broadcom Integrated NIC Management Firmware 1.x before 1.40.0.0 and 8.x before 8.08 on the HP Small Form Factor and Microtower platforms allows remote attackers to execute arbitrary code via unknown vectors.

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

It affects 1 product.


Products: Broadcom Broadcom.

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

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

## Is CVE-2010-0104 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0104 is a critical code injection vulnerability in n/a, published on 18 Mar 2010. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0104 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-0104/ (Markdown: https://insights.sbomify.com/CVE-2010-0104/index.md)
```

## Sources

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

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