Mac Os XOperating system · Apple

CVE-2013-0984

HIGH · 9.3 CVSS v2.0 Published 2013-06-05
Fix available
A fix is available. Upgrade to after 10.6.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Directory Service in Apple Mac OS X through 10.6.8 allows remote attackers to execute arbitrary code or cause a denial of service (daemon crash) via a crafted message.

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 · low confidence

Directory Service in Apple Mac OS X through 10.6.8 contains a vulnerability that allows remote attackers to send a crafted message leading to arbitrary code execution or denial of service via daemon crash. The CVSS 9.3 indicates a critical buffer overflow or injection flaw in the network-facing Directory Service daemon.

MitigationUpgrade from Mac OS X 10.6.8 to a supported version, or if upgrade is not feasible, disable or restrict access to Directory Service and implement network segmentation to limit exposure to untrusted networks.

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
Mac Os XOperating system
Affected:<= 10.6.8= 10.0.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.1.0= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5
Mac Os X ServerOperating system
Affected:<= 10.6.8= 10.0= 10.0.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.1= 10.1.0= 10.1.1= 10.1.2= 10.1.3

CVSS 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Mac OS X version
    Run 'sw_vers -productVersion' in Terminal or view About This Mac
    Affected if Version is 10.6.8 or lower, or matches any of these specific versions: 10.0.0, 10.0.1, 10.0.2, 10.0.3, 10.0.4, 10.1.0, 10.1.1, 10.1.2, 10.1.3, 10.1.4, 10.1.5 (for Mac OS X); or 10.0, 10.0.0-10.0.4, 10.1, 10.1.0-10.1.3 (for Mac OS X Server)
  2. Verify Directory Service daemon is running
    Run 'ps aux | grep -i directoryd' or 'sudo launchctl list | grep -i com.apple DirectoryServices'
    Affected if The DirectoryService daemon (directoryd) is actively running on the system
  3. Check if Directory Service is network-exposed
    Run 'sudo lsof -i -P | grep 625' or 'sudo netstat -an | grep 625' to check if port 625 (default Directory Service port) is listening
    Affected if Directory Service is bound to a network interface and accepting connections on port 625 or other ports

Your environment is affected if you are running Mac OS X or Mac OS X Server version 10.6.8 or earlier AND the Directory Service daemon is running and exposed on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 10.6.8
Interim mitigation

Upgrade from Mac OS X 10.6.8 to a supported version, or if upgrade is not feasible, disable or restrict access to Directory Service and implement network segmentation to limit exposure to untrusted networks.

Recommended fix High confidence

Mac OS X 10.7 (Lion) or later; for Server, upgrade to Mac OS X Server 10.7 or later. Apple released Security Update 2013-001 for 10.6.8 as the immediate patch.

  1. Identify the current Mac OS X version by clicking Apple menu > About This Mac
  2. Back up all important data using Time Machine or another backup solution
  3. Download and install the latest available Mac OS X upgrade from the Apple App Store or support.apple.com
  4. After upgrading, verify the Directory Service is running by opening Terminal and running: sudo serveradmin start directory
  5. Confirm the fix by checking Apple menu > About This Mac shows a version newer than 10.6.8
Caveat Upgrading from Mac OS X 10.6.8 (Snow Leopard) to a newer version may cause incompatibility with older applications designed for PowerPC or 32-bit only software. Some legacy hardware may not be supported in newer OS versions.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mac Os X Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0984 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0984 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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