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

> Remote attackers can cause a denial of service in the BIND named daemon by exploiting the maxdname parameter.

- **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 Jan 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-4hq8-3ffh-25xf

## What is CVE-1999-0849?

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

### Official description

Denial of service in BIND named via maxdname.

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

It affects 1 product.


Products: Isc Bind.

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

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

## Is CVE-1999-0849 being exploited?

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

## Other vulnerabilities in Isc Bind

- [CVE-2008-0122](https://insights.sbomify.com/CVE-2008-0122/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0010](https://insights.sbomify.com/CVE-2001-0010/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0011](https://insights.sbomify.com/CVE-2001-0011/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0013](https://insights.sbomify.com/CVE-2001-0013/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-1029](https://insights.sbomify.com/CVE-2000-1029/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0849 is a medium-severity denial of service vulnerability in Isc Bind, published on 4 Jan 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-0849 in the wild and no public exploit code.

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

## Sources

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

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