CVE-2007-3828
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 · uneditedUnspecified vulnerability in mDNSResponder in Apple Mac OS X allows remote attackers to execute arbitrary code via unspecified vectors, a related issue to CVE-2007-2386.
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 confidencemDNSResponder in Apple Mac OS X contains an unspecified vulnerability allowing remote attackers to execute arbitrary code via unspecified vectors. This is related to CVE-2007-2386 and represents a critical remote code execution flaw in Apple's Bonjour/mDNS service.
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.8= 10.4.9= 10.4.10CVSS 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
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/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 Mac OS X versionRun 'sw_vers' or check System Preferences > About to determine the exact Mac OS X version numberAffected if The version is any of 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, 10.4.9, or 10.4.10
-
Confirm mDNSResponder is runningRun 'ps -ef | grep mDNSResponder' or check Activity Monitor for the mDNSResponder processAffected if The mDNSResponder process is active, indicating the vulnerable service is exposed
-
Verify mDNSResponder executable existsCheck for the mDNSResponder binary in the system, typically located in /usr/sbin/ or /usr/bin/Affected if The mDNSResponder binary is present on the system
-
Check network exposure of mDNSResponderRun 'lsof -i -P | grep mDNSResponder' or 'netstat -an | grep 5353' to see if port 5353 (mDNS) is listeningAffected if Port 5353 is open and listening, making the service network-accessible
A system is affected if it runs Mac OS X 10.4.x with mDNSResponder active and exposed on the 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 updates for the affected Mac OS X version to patch mDNSResponder, or upgrade to a supported OS version; network segmentation can limit exposure for unpatched legacy systems.
macOS 10.5 (Leopard) or later supported version - Apple Security Update 2007-005 addressed this and related vulnerabilities
- 1. Back up all critical data on the affected Mac system before making any changes
- 2. Since Mac OS X 10.4.x reached end-of-life, obtain a licensed copy of a supported macOS version (10.5 or later) or acquire a newer Mac capable of running a supported macOS version
- 3. Perform a clean installation or Time Machine restore of the new macOS version
- 4. After upgrade, verify mDNSResponder is updated by checking System Preferences > Network > DNS tab and ensuring Bonjour is functioning properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3828 — 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-3828 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