CVE-2007-2386
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 · uneditedBuffer overflow in mDNSResponder in Apple Mac OS X 10.4 up to 10.4.9 allows remote attackers to cause a denial of service (application termination) or execute arbitrary code via a crafted UPnP Internet Gateway Device (IGD) 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 confidenceBuffer overflow vulnerability in mDNSResponder (Apple's Bonjour/mDNS service) on Mac OS X 10.4 through 10.4.9 allows remote attackers to execute arbitrary code or cause denial of service via specially crafted UPnP Internet Gateway Device (IGD) packets sent to the affected system.
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= 10.4= 10.4.1= 10.4.2= 10.4.3= 10.4.4= 10.4.5= 10.4.6= 10.4.7= 10.4.8CVSS 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:N/A:C
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.
-
Identify the Mac OS X versionRun 'sw_vers' or go to Apple menu > About This Mac to determine the exact version numberAffected if The version is 10.4.0 through 10.4.9 (10.4, 10.4.1, 10.4.2, 10.4.3, 10.4.4, 10.4.5, 10.4.6, 10.4.7, 10.4.8, or 10.4.9)
-
Verify mDNSResponder service is runningRun 'ps -ax | grep mDNSResponder' in Terminal to check if the process is activeAffected if mDNSResponder is running and exposed to network traffic
-
Confirm UPnP IGD (Internet Gateway Device) functionality is enabledCheck System Preferences > Sharing > Internet Sharing or AirPort settings for UPnP-enabled sharing options. On command line, inspect the state of the mDNSResponder configuration or any NAT/port forwarding configurations that expose UPnP servicesAffected if UPnP/IGD discovery or sharing is enabled, allowing external packets to reach the mDNSResponder service
You are affected if you are running Mac OS X 10.4 through 10.4.9 with mDNSResponder active and UPnP/IGD functionality enabled on your network.
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.
dbcve · scopedApply Apple security update 2007-006 or upgrade to Mac OS X 10.4.10 or later. Since Mac OS X 10.4 is end-of-life, consider migrating to a supported macOS version if still running this legacy system.
Mac OS X 10.4.10 or later (preferably upgrade to macOS 10.5 or newer if hardware supports it)
- 1. Back up all critical data before performing any system update
- 2. Identify the current Mac OS X version by clicking Apple menu > About This Mac
- 3. If running Mac OS X 10.4.x (10.4, 10.4.1, 10.4.2, 10.4.3), upgrade to a supported macOS version
- 4. For Macs capable of running later versions, upgrade to macOS 10.5 (Leopard) or newer, which includes the fix for this vulnerability in mDNSResponder
- 5. After upgrading, verify the system is running a patched version by checking Software Update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2386 — 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-2007-2386 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