CVE-2015-1132
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 · uneditedfontd in Apple Type Services (ATS) in Apple OS X before 10.10.3 allows local users to gain privileges via unspecified vectors, a different vulnerability than CVE-2015-1131, CVE-2015-1133, CVE-2015-1134, and CVE-2015-1135.
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 confidencefontd in Apple Type Services (ATS) in OS X before 10.10.3 contains a local privilege escalation vulnerability allowing unprivileged local users to gain elevated system privileges through unspecified vectors in the font processing subsystem.
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
- 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.
-
Check OS X versionRun 'sw_vers -productVersion' in Terminal or check System Preferences > About > VersionAffected if Version is below 10.10.3 (e.g., 10.10.2, 10.10.1, 10.10.0, etc.)
-
Verify fontd component versionCheck /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd for existence; note that version inspection requires deep system tools and is not practical for manual checksAffected if Running any OS X version prior to 10.10.3 indicates vulnerable fontd component
-
Confirm local access requirementVerify this is a local-only attack requiring prior user authentication to the systemAffected if Systems without local user accounts are at lower risk, but still vulnerable if anyone can authenticate
If the installed OS X version is 10.10.3 or later, the environment is not affected; versions below 10.10.3 contain the vulnerable fontd component and are affected.
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 OS X 10.10.3 or later which contains the patched fontd component; this is a local attack requiring prior authentication, so prioritize patching systems with direct user access.
Mac OS X 10.10.3 (Yosemite) or later; recommended: latest supported macOS (currently macOS Sonoma)
- Backup all important data before performing system updates
- Upgrade Mac OS X to version 10.10.3 or later. Note: Apple has since released much newer macOS versions with additional security fixes; consider upgrading to the latest supported macOS release for comprehensive protection
- After upgrading, verify the system is running version 10.10.3 or higher by clicking Apple menu > About This Mac
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1132 — 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-1132 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