# CVE-2005-0263: Memory corruption in n/a

> Local attackers can execute arbitrary code via a buffer overflow in the netpmon utility on AIX systems.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/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:** No
- **Published:** 10 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9585-ghrc-cx9g

## What is CVE-2005-0263?

CVE-2005-0263 is a high-severity memory corruption vulnerability in Ibm Aix, published on 10 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in netpmon on AIX 5.1, 5.2, and 5.3 allows local users to execute arbitrary code via a long -O argument.

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

It affects 1 product.


Products: Ibm Aix.

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

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

## Is CVE-2005-0263 being exploited?

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

Public exploit code:

- AIX 5.2 - 'netpmon' Local Privilege Escalation (exploitdb)

## Other vulnerabilities in Ibm Aix

- [CVE-2025-36250](https://insights.sbomify.com/CVE-2025-36250/): AIX Code Execution (critical 10.0)
- [CVE-2024-56346](https://insights.sbomify.com/CVE-2024-56346/): IBM AIX command execution (critical 10.0)
- [CVE-2010-3187](https://insights.sbomify.com/CVE-2010-3187/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-3699](https://insights.sbomify.com/CVE-2009-3699/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-3517](https://insights.sbomify.com/CVE-2009-3517/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0263 is a high-severity memory corruption vulnerability in Ibm Aix, published on 10 Feb 2005. 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-2005-0263 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-2005-0263/ (Markdown: https://insights.sbomify.com/CVE-2005-0263/index.md)
```

## Sources

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

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