# CVE-2006-5792: Other in n/a

> Remote attackers can execute arbitrary code on XLink Omni-NFS Enterprise via unspecified vectors, posing a critical risk to NFS server deployments.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pfvq-g54v-5qgj

## What is CVE-2006-5792?

CVE-2006-5792 is a high-severity vulnerability in n/a, published on 7 Nov 2006. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in XLink Omni-NFS Enterprise allows remote attackers to execute arbitrary code via unspecified vectors, as demonstrated by vd_xlink2.pm, an "Omni-NFS Enterprise remote exploit." NOTE: this is probably a different vulnerability than CVE-2006-5780. As of 20061107, this disclosure has no actionable information. However, since it is from a reliable researcher, it is being assigned a CVE identifier for tracking purposes.

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

It affects 1 product.


Products: Xlink Technology Omni-Nfs X Enterprise.

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

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

## Is CVE-2006-5792 being exploited?

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

Public exploit code:

- Xlink FTP Client Buffer Overflow (metasploit)
- Xlink FTP Server Buffer Overflow (metasploit)
- Xlink FTP Server - Remote Buffer Overflow (Metasploit) (exploitdb)
- Xlink FTP Client - Remote Buffer Overflow (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-1999-1349](https://insights.sbomify.com/CVE-1999-1349/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5792 is a high-severity vulnerability in n/a, published on 7 Nov 2006. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5792 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-5792/ (Markdown: https://insights.sbomify.com/CVE-2006-5792/index.md)
```

## Sources

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

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