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

> Remote attackers can execute arbitrary code on Novell NetIdentity Client by sending malicious RPC messages to a named pipe.

- **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:** 21 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x4fx-ff3q-q3hv

## What is CVE-2009-1350?

CVE-2009-1350 is a critical memory corruption vulnerability in n/a, published on 21 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in xtagent.exe in Novell NetIdentity Client before 1.2.4 allows remote attackers to execute arbitrary code by establishing an IPC$ connection to the XTIERRPCPIPE named pipe, and sending RPC messages that trigger a dereference of an arbitrary pointer.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Novell Netidentity Client1.2.3.

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

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

## Is CVE-2009-1350 being exploited?

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

Public exploit code:

- Novell NetIdentity Agent XTIERRPCPIPE Named Pipe Buffer Overflow (metasploit)
- Novell NetIdentity Agent - XTIERRPCPIPE Named Pipe Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1350 is a critical memory corruption vulnerability in n/a, published on 21 Apr 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-1350 exists.

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-2009-1350/ (Markdown: https://insights.sbomify.com/CVE-2009-1350/index.md)
```

## Sources

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

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