CVE-2014-1318
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 Intel Graphics Driver in Apple OS X through 10.9.2 does not properly validate a certain pointer, which allows attackers to execute arbitrary code via a crafted application.
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 confidenceA vulnerability in the Intel Graphics Driver for Apple OS X through version 10.9.2 involves improper pointer validation, which can be exploited by a crafted application to achieve arbitrary code execution. This is a kernel-level driver flaw allowing privilege escalation.
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.9.2= 10.9= 10.9.1= 10.8.0= 10.8.1= 10.8.2= 10.8.3= 10.8.4= 10.8.5CVSS 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 your macOS versionRun 'sw_vers -productVersion' in Terminal to get the exact OS version numberAffected if The version is 10.9.2 or lower, or matches 10.9, 10.9.1, 10.8.0, 10.8.1, 10.8.2, 10.8.3, 10.8.4, or 10.8.5 exactly
-
Verify Intel Graphics hardware is presentRun 'system_profiler SPDisplaysDataType' to list graphics hardware. Look for Intel integrated graphics (Intel HD, Intel Iris, etc.)Affected if The system has Intel integrated graphics processors (Intel HD 3000, 4000, 5000, etc.)
-
Confirm the graphics kernel extension is loadedRun 'kextstat | grep -i intel' to list loaded Intel kernel extensions. Look for AppleIntelHDGraphics or AppleIntelIGFXAffected if An Intel graphics driver kernel extension (AppleIntelHDGraphics.kext or similar) is loaded in the kernel
You are affected if your macOS version falls within the 10.8.x through 10.9.2 range AND your system uses an Intel integrated graphics driver, because the vulnerability exists in that specific driver component.
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 the Apple security update that patches the Intel Graphics Driver (OS X 10.9.3 or later includes the fix). Verify graphics functionality after patching.
OS X 10.9.3 or later (or migrate to a later OS X release that includes the security fix)
- Back up all important data on the Mac before performing any system update
- Verify the current OS X version by clicking the Apple menu and selecting 'About This Mac'
- Download and install the latest available OS X version (or the latest security update for your OS X release line from Apple Support)
- Restart the system when prompted to complete the installation
- After updating, verify the Intel Graphics Driver has been updated by checking System Information under 'Graphics/Display'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1318 — 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-2014-1318 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