# CVE-2011-0220: Denial of service in Bonjour

> A crafted multicast DNS packet can crash Apple Bonjour, causing a denial of service for users of the affected library.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cqq5-x4gj-94gm

## What is CVE-2011-0220?

CVE-2011-0220 is a medium-severity denial of service vulnerability in Apple Bonjour, published on 5 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Apple Bonjour before 2011 allows a crash via a crafted multicast DNS packet.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-0220?

It affects 1 product.


Products: Apple Bonjour.

## How do I fix CVE-2011-0220?

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

## Is CVE-2011-0220 being exploited?

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

## Other vulnerabilities in Apple Bonjour

- [CVE-2008-3630](https://insights.sbomify.com/CVE-2008-3630/): Other in n/a (medium 6.4)
- [CVE-2008-2326](https://insights.sbomify.com/CVE-2008-2326/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0220 and fix it if it is affected.

What it is: CVE-2011-0220 is a medium-severity denial of service vulnerability in Apple Bonjour, published on 5 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-0220 in the wild and no public exploit code.

Affected product: Apple Bonjour. 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-2011-0220/ (Markdown: https://insights.sbomify.com/CVE-2011-0220/index.md)
```

## Sources

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

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