# CVE-2009-3699: Memory corruption in n/a

> Remote attackers can execute arbitrary code on IBM AIX systems via a stack-based buffer overflow in the calendar daemon library.

- **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:** 15 Oct 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jc9g-5ggm-9q3r

## What is CVE-2009-3699?

CVE-2009-3699 is a critical memory corruption vulnerability in Ibm Aix, published on 15 Oct 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in libcsa.a (aka the calendar daemon library) in IBM AIX 5.x through 5.3.10 and 6.x through 6.1.3, and VIOS 2.1 and earlier, allows remote attackers to execute arbitrary code via a long XDR string in the first argument to procedure 21 of rpc.cmsd.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2009-3699?

It affects 2 products.


Products: Ibm Aix, Ibm Vios.

## How do I fix CVE-2009-3699?

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

## Is CVE-2009-3699 being exploited?

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

Public exploit code:

- AIX Calendar Manager Service Daemon (rpc.cmsd) Opcode 21 Buffer Overflow (metasploit)
- AIX Calendar Manager Service Daemon (rpc.cmsd) Opcode 21 - Buffer Overflow (Metasploit) (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-3517](https://insights.sbomify.com/CVE-2009-3517/): Auth bypass in n/a (critical 10.0)
- [CVE-2006-5008](https://insights.sbomify.com/CVE-2006-5008/): Command injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3699 and fix it if it is affected.

What it is: CVE-2009-3699 is a critical memory corruption vulnerability in Ibm Aix, published on 15 Oct 2009. 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-2009-3699 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-2009-3699/ (Markdown: https://insights.sbomify.com/CVE-2009-3699/index.md)
```

## Sources

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

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