# CVE-2010-0412: Command injection in n/a

> Attackers can execute arbitrary commands via the make program by exploiting improper restriction of the build option in SystemTap server.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-0412, GHSA-3274-qhqf-766c

## What is CVE-2010-0412?

CVE-2010-0412 is a high-severity command injection vulnerability in n/a, published on 25 Feb 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

stap-server in SystemTap 1.1 does not properly restrict the value of the -B (aka BUILD) option, which allows attackers to have an unspecified impact via vectors associated with executing the make program, a different vulnerability than CVE-2009-4273.

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

It affects 1 product.


Products: Systemtap Systemtap.

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

Upgrade to a fixed version.

## Is CVE-2010-0412 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4273](https://insights.sbomify.com/CVE-2009-4273/): Command injection in n/a (critical 10.0)
- [CVE-2010-4170](https://insights.sbomify.com/CVE-2010-4170/): Privilege escalation in n/a (high 7.2)
- [CVE-2012-0875](https://insights.sbomify.com/CVE-2012-0875/): Information disclosure in n/a (medium 5.4)
- [CVE-2010-0411](https://insights.sbomify.com/CVE-2010-0411/): Integer overflow in n/a (medium 4.9)
- [CVE-2011-2502](https://insights.sbomify.com/CVE-2011-2502/): Privilege escalation in n/a (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0412 is a high-severity command injection vulnerability in n/a, published on 25 Feb 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0412 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-0412/ (Markdown: https://insights.sbomify.com/CVE-2010-0412/index.md)
```

## Sources

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

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