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

> Attackers can cause denial of service in MDaemon WorldClient and WebConfig services by sending a long URL.

- **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-4v7m-9h3p-c5mq

## What is CVE-1999-0844?

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

### Official description

Denial of service in MDaemon WorldClient and WebConfig services via a long URL.

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

It affects 1 product.


Products: Deerfield Mdaemon.

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

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

## Is CVE-1999-0844 being exploited?

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

Public exploit code:

- Alt-N MDaemon 2.8.5 - WebConfig Overflow Denial of Service (exploitdb)
- Alt-N WorldClient Pro 2.0.0.0/2.0.1.0/Standard 2.0.0.0 - Long URL Denial of Service (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0844 is a medium-severity denial of service vulnerability in n/a, published on 4 Feb 2000. 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-1999-0844 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-1999-0844/ (Markdown: https://insights.sbomify.com/CVE-1999-0844/index.md)
```

## Sources

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

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