CVE-2011-0220
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApple Bonjour before 2011 allows a crash via a crafted multicast DNS packet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceApple Bonjour (mDNSResponder) before 2011 contains a vulnerability in its multicast DNS packet handling that allows a remote attacker to cause a denial of service via a crafted malicious mDNS packet.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2011CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify mDNSResponder service is runningOn macOS: ps aux | grep mDNSResponder. On Windows: check Services for 'Bonjour Service' or 'mDNSResponder'Affected if mDNSResponder process is active and running on the system
-
Determine mDNSResponder versionOn macOS: /usr/sbin/mDNSResponder -version or ls -la /usr/sbin/mDNSResponder. On Windows: right-click the Bonjour service exe in Program Files and check Properties > Details for version infoAffected if Version date is earlier than 2011 or version string indicates pre-2011 release
-
Check Bonjour installation dateOn macOS: ls -la /usr/sbin/mDNSResponder or check System Information > Software > Installations. On Windows: check file properties of mDNSResponder.exe in Program FilesAffected if Installation or binary creation date is before 2011
-
Verify mDNS multicast listening is enabledCheck if port 5353/udp is open and listening: sudo lsof -i :5353 -P -n on macOS, or netstat -an | findstr 5353 on WindowsAffected if mDNSResponder is actively listening on multicast address 224.0.0.251 port 5353
The system is affected if mDNSResponder/Bonjour is running and its version or installation date predates 2011, exposing the multicast DNS service to the denial-of-service vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2011
Update Apple Bonjour/mDNSResponder to a version released after 2011, or apply the relevant Apple security update.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-0220 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data