# CVE-2010-0411: Integer overflow in n/a

> Local attackers can cause a system crash or hang via integer overflow in SystemTap when processing processes with many arguments.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-0411, GHSA-h63c-ff5w-hmx7, RHSA-2010:0125

## What is CVE-2010-0411?

CVE-2010-0411 is a medium-severity vulnerability in n/a, published on 8 Feb 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple integer signedness errors in the (1) __get_argv and (2) __get_compat_argv functions in tapset/aux_syscalls.stp in SystemTap 1.1 allow local users to cause a denial of service (script crash, or system crash or hang) via a process with a large number of arguments, leading to a buffer overflow.

Weakness: CWE-189

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `systemtap` | Red Hat:enterprise_linux:4::as | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-runtime` | Red Hat:enterprise_linux:4::as | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-testsuite` | Red Hat:enterprise_linux:4::as | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-runtime` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-testsuite` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap` | Red Hat:enterprise_linux:4::es | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-runtime` | Red Hat:enterprise_linux:4::es | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-testsuite` | Red Hat:enterprise_linux:4::es | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-runtime` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.6.2-2.el4_8.1 |
| `systemtap-testsuite` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.6.2-2.el4_8.1 |

Products: Systemtap Systemtap.

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

Apply the vendor's patch.

## Is CVE-2010-0411 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0411 exists.

Public exploit code:

- SystemTap 1.0/1.1 - '__get_argv()' / '__get_compat_argv()' Local Memory Corruption (exploitdb)

## 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-0412](https://insights.sbomify.com/CVE-2010-0412/): Command injection in n/a (high 7.5)
- [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-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-0411 and fix it if it is affected.

What it is: CVE-2010-0411 is a medium-severity vulnerability in n/a, published on 8 Feb 2010. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0411 exists.

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-0411/ (Markdown: https://insights.sbomify.com/CVE-2010-0411/index.md)
```

## Sources

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

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