# CVE-2006-5780: Memory corruption in n/a

> Remote attackers can execute arbitrary code on XLink Omni-NFS Server via a stack-based buffer overflow in the NFS daemon.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vpmf-9mwj-7fq6

## What is CVE-2006-5780?

CVE-2006-5780 is a high-severity memory corruption vulnerability in n/a, published on 7 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in nfsd.exe in XLink Omni-NFS Server 5.2 allows remote attackers to execute arbitrary code via a crafted TCP packet to port 2049 (nfsd), as demonstrated by vd_xlink.pm.

## Which versions are affected by CVE-2006-5780?

It affects 1 product.


Products: Xlink Technology Omni-Nfs Server.

## How do I fix CVE-2006-5780?

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

## Is CVE-2006-5780 being exploited?

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

Public exploit code:

- Omni-NFS Server 5.2 - 'nfsd.exe' Remote Stack Overflow (Metasploit) (exploitdb)
- Omni-NFS Server Buffer Overflow (metasploit)
- Omni-NFS Server - Remote Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5780 and fix it if it is affected.

What it is: CVE-2006-5780 is a high-severity memory corruption vulnerability in n/a, published on 7 Nov 2006. 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-2006-5780 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-2006-5780/ (Markdown: https://insights.sbomify.com/CVE-2006-5780/index.md)
```

## Sources

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

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