# CVE-2010-1039: Memory corruption in n/a

> Remote attackers can execute arbitrary code via format string specifiers in RPC requests to rpc.pcnfsd on affected Unix systems.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-599v-778r-52j4

## What is CVE-2010-1039?

CVE-2010-1039 is a critical memory corruption vulnerability in Ibm Aix, published on 20 May 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in the _msgout function in rpc.pcnfsd in IBM AIX 6.1, 5.3, and earlier; IBM VIOS 2.1, 1.5, and earlier; NFS/ONCplus B.11.31_09 and earlier on HP HP-UX B.11.11, B.11.23, and B.11.31; and SGI IRIX 6.5 allows remote attackers to execute arbitrary code via an RPC request containing format string specifiers in an invalid directory name.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 4 products.


Products: Hp Nfs\/Oncplus, Ibm Aix, Ibm Vios, Sgi Irix.

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

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

## Is CVE-2010-1039 being exploited?

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

Public exploit code:

- rpc.pcnfsd - Remote Format String (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-1039 is a critical memory corruption vulnerability in Ibm Aix, published on 20 May 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-1039 exists.

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

## Sources

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

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