# CVE-2005-2811: Privilege escalation in n/a

> Local attackers can gain privileges via insecure Perl module paths in Net-SNMP on Gentoo Linux.

- **Severity:** Medium 4.6 (`AV:L/AC:L/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:** No
- **Published:** 7 Sep 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w7p9-h59x-gp43

## What is CVE-2005-2811?

CVE-2005-2811 is a medium-severity vulnerability in n/a, published on 7 Sep 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path vulnerability in Net-SNMP 5.2.1.2 and earlier, on Gentoo Linux, installs certain Perl modules with an insecure DT_RPATH, which could allow local users to gain privileges.

## Which versions are affected by CVE-2005-2811?

It affects 1 product.


Products: Net-Snmp Net-Snmp.

## How do I fix CVE-2005-2811?

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

## Is CVE-2005-2811 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4837](https://insights.sbomify.com/CVE-2005-4837/): Use after free in n/a (critical 10.0)
- [CVE-2005-1740](https://insights.sbomify.com/CVE-2005-1740/): Path traversal in n/a (critical 10.0)
- [CVE-2007-5846](https://insights.sbomify.com/CVE-2007-5846/): Denial of service in n/a (high 7.8)
- [CVE-2018-18066](https://insights.sbomify.com/CVE-2018-18066/): Null dereference in n/a (high 7.5)
- [CVE-2015-5621](https://insights.sbomify.com/CVE-2015-5621/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2811 and fix it if it is affected.

What it is: CVE-2005-2811 is a medium-severity vulnerability in n/a, published on 7 Sep 2005. 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-2005-2811 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-2005-2811/ (Markdown: https://insights.sbomify.com/CVE-2005-2811/index.md)
```

## Sources

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

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