# CVE-1999-1349: Denial of service in n/a

> Remote attackers can cause denial of service in Omni-NFS/X via crafted packets to port 111, affecting NFS server availability.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 12 Sep 2001
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-hv9m-2rcj-rh9v

## What is CVE-1999-1349?

CVE-1999-1349 is a medium-severity denial of service vulnerability in n/a, published on 12 Sep 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NFS daemon (nfsd.exe) for Omni-NFS/X 6.1 allows remote attackers to cause a denial of service (resource exhaustion) via certain packets, possibly with the Urgent (URG) flag set, to port 111.

## Which versions are affected by CVE-1999-1349?

It affects 1 product.


Products: Xlink Technology Omni-Nfs X Enterprise.

## How do I fix CVE-1999-1349?

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

## Is CVE-1999-1349 being exploited?

There is no known exploitation of CVE-1999-1349 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2006-5792](https://insights.sbomify.com/CVE-2006-5792/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-1349 and fix it if it is affected.

What it is: CVE-1999-1349 is a medium-severity denial of service vulnerability in n/a, published on 12 Sep 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-1999-1349 in the wild and no public exploit code.

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

## Sources

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

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