# CVE-2008-2326: Null dereference in n/a

> Attackers can crash the Bonjour service on Windows by sending a crafted .local domain name with a long label, causing a denial of service.

- **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:** 10 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mgq3-vvm3-gj5g

## What is CVE-2008-2326?

CVE-2008-2326 is a medium-severity vulnerability in n/a, published on 10 Sep 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mDNSResponder in the Bonjour Namespace Provider in Apple Bonjour for Windows before 1.0.5 allows attackers to cause a denial of service (NULL pointer dereference and application crash) by resolving a crafted .local domain name that contains a long label.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-2326?

It affects 1 product.


Products: Apple Bonjour.

## How do I fix CVE-2008-2326?

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

## Is CVE-2008-2326 being exploited?

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

Public exploit code:

- Apple Bonjour for Windows 1.0.4 - mDNSResponder Null Pointer Dereference Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-3630](https://insights.sbomify.com/CVE-2008-3630/): Other in n/a (medium 6.4)
- [CVE-2011-0220](https://insights.sbomify.com/CVE-2011-0220/): Denial of service in Bonjour (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2326 and fix it if it is affected.

What it is: CVE-2008-2326 is a medium-severity vulnerability in n/a, published on 10 Sep 2008. 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-2008-2326 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-2008-2326/ (Markdown: https://insights.sbomify.com/CVE-2008-2326/index.md)
```

## Sources

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

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