CVE-2015-1130
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 · uneditedThe XPC implementation in Admin Framework in Apple OS X before 10.10.3 allows local users to bypass authentication and obtain admin privileges via unspecified vectors.
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 confidenceThe vulnerability exists in the XPC (inter-process communication) implementation within the Admin Framework on Apple OS X systems prior to version 10.10.3. Local attackers can exploit unspecified vectors in the XPC service to bypass authentication mechanisms and elevate their privileges to administrator level, achieving full admin access to the 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.10.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Check installed OS X versionOpen Terminal and run: sw_vers -productVersionAffected if The version displayed is less than 10.10.3 (for example, 10.10.2, 10.10.1, or 10.10.0)
-
Verify Admin Framework XPC service availabilityList running XPC services by examining /System/Library/Frameworks/Admin.framework and checking for admin-related XPC services in the launchd process list using: sudo launchctl list | grep -i adminAffected if The system is running an affected version and admin-related XPC services are active
-
Confirm user privilege contextCheck current user privileges by running: whoami and groupsAffected if The user is not already an administrator (this is the prerequisite condition for the exploit to be usable for privilege escalation)
The environment is affected if OS X version is below 10.10.3 and admin XPC services are accessible to unprivileged local users.
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 · scoped10.10.3
Apply the vendor patch by upgrading to OS X 10.10.3 or later, which contains the corrected XPC authentication implementation in the Admin Framework.
Mac OS X 10.10.3 or later (or current supported macOS version)
- Back up important data on the Mac before performing any system update
- Open the Apple menu and select 'Software Update' to check for available updates
- Install Mac OS X 10.10.3 or later (or install all available security updates from Apple)
- Restart the system when prompted to complete the installation
- Verify the update was successful by checking System Preferences > About > Version (should show 10.10.3 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1130 — 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-2015-1130 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