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

> Remote attackers can cause denial of service on Novell NetWare web servers by sending a large number of HTTP GET requests.

- **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:** 4 Feb 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-gmwm-6jxm-47j7

## What is CVE-1999-0929?

CVE-1999-0929 is a medium-severity denial of service vulnerability in Novell Netware, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Novell NetWare with Novell-HTTP-Server or YAWN web servers allows remote attackers to conduct a denial of service via a large number of HTTP GET requests.

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

It affects 2 products.


Products: Novell Http Server, Novell Netware.

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

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

## Is CVE-1999-0929 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0929 is a medium-severity denial of service vulnerability in Novell Netware, published on 4 Feb 2000. 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-0929 in the wild and no public exploit code.

Affected product: Novell Netware. 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-0929/ (Markdown: https://insights.sbomify.com/CVE-1999-0929/index.md)
```

## Sources

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

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