# CVE-2011-2502: Privilege escalation in n/a

> Local users in the stapusr group can gain privileges by exploiting improper module validation in the SystemTap runtime tool.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 26 Jul 2012
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2011-2502, GHSA-gmjv-9hc6-6rf5

## What is CVE-2011-2502?

CVE-2011-2502 is a medium-severity vulnerability in n/a, published on 26 Jul 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

runtime/staprun/staprun_funcs.c in the systemtap runtime tool (staprun) in SystemTap before 1.6 does not properly validate modules when a module path is specified by a user for user-space probing, which allows local users in the stapusr group to gain privileges via a crafted module in the search path in the -u argument.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-2502?

It affects 1 product.


Products: Systemtap Systemtap.

## How do I fix CVE-2011-2502?

Upgrade to a fixed version.

## Is CVE-2011-2502 being exploited?

There is no known exploitation of CVE-2011-2502 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-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-2010-0411](https://insights.sbomify.com/CVE-2010-0411/): Integer overflow in n/a (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2502 and fix it if it is affected.

What it is: CVE-2011-2502 is a medium-severity vulnerability in n/a, published on 26 Jul 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2502 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-2011-2502/ (Markdown: https://insights.sbomify.com/CVE-2011-2502/index.md)
```

## Sources

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

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