# CVE-2010-2064: Path traversal in rpcbind

> Local attackers can exploit symlink vulnerabilities in rpcbind to write arbitrary files and escalate privileges.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 29 Oct 2019
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-2064, GHSA-43c2-9xgq-4pm4

## What is CVE-2010-2064?

CVE-2010-2064 is a high-severity path traversal vulnerability in rpcbind, published on 29 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

rpcbind 0.2.0 allows local users to write to arbitrary files or gain privileges via a symlink attack on (1) /tmp/portmap.xdr and (2) /tmp/rpcbind.xdr.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Rpcbind Project Rpcbind.

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

Apply the vendor's patch.

## Is CVE-2010-2064 being exploited?

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

## Other vulnerabilities in rpcbind

- [CVE-2010-2061](https://insights.sbomify.com/CVE-2010-2061/): Path traversal in rpcbind (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2064 is a high-severity path traversal vulnerability in rpcbind, published on 29 Oct 2019. 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-2010-2064 in the wild and no public exploit code.

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

## Sources

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

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