dbcve.org
Mac Os XOperating system · Apple

CVE-2014-1376

HIGH · 10.0 CVSS v2.0 Published 2014-07-01
Fix available
A fix is available. Upgrade to after 10.9.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Intel Compute in Apple OS X before 10.9.4 does not properly restrict an unspecified OpenCL API call, 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 · low confidence

Vulnerability in Intel Compute driver in Apple OS X versions prior to 10.9.4 allows improper access to an OpenCL API function, enabling a malicious application to execute arbitrary code with elevated privileges.

MitigationApply Apple OS X security update 10.9.4 or later which contains the fixed Intel Compute driver; ensure OpenCL applications are only run from trusted sources.

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.9.3= 10.8.0= 10.8.1= 10.8.2= 10.8.3= 10.8.4= 10.8.5= 10.9= 10.9.1= 10.9.2

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
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 checks

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

  1. Check installed OS X version
    Go to Apple menu > About This Mac to view the OS X version number
    Affected if The version is 10.9.3 or earlier, or specifically 10.8.0 through 10.9.2 as listed in affected versions
  2. Verify Intel Compute driver presence
    Check system for Intel Compute driver components (the specific driver file path may vary; consult Intel or Apple documentation for your system)
    Affected if The Intel Compute driver is installed and the OS version is within the affected range
  3. Confirm OpenCL is accessible
    Verify OpenCL framework is available on the system (OpenCL is typically included in macOS but verify it is not explicitly disabled)
    Affected if OpenCL is enabled or accessible and the OS version is vulnerable
  4. Check if security update 10.9.4 or later is applied
    Review installed updates or compare current version to 10.9.4 to determine if the patched version is running
    Affected if The system is running a version prior to 10.9.4 and has not received the security update

A user is affected if they are running any OS X version from 10.8.0 through 10.9.3 with the Intel Compute driver and OpenCL enabled, and have not applied the 10.9.4 or later security update.

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.9.3
Interim mitigation

Apply Apple OS X security update 10.9.4 or later which contains the fixed Intel Compute driver; ensure OpenCL applications are only run from trusted sources.

Recommended fix High confidence

OS X 10.9.4 (Mavericks) or later; for 10.8.x users, upgrade to 10.9.4+ or to latest supported OS (El Capitan 10.11.x for older hardware)

  1. 1. Back up your current system using Time Machine or another backup solution.
  2. 2. Verify current OS X version by clicking Apple menu > About This Mac.
  3. 3. For Mac OS X 10.8.0-10.8.2: Upgrade to OS X 10.9.4 or later (Mavericks). Note: Apple no longer provides free upgrades from 10.8; you may need to purchase from Mac App Store or obtain through other legitimate channels.
  4. 4. For Mac OS X 10.9.x up to 10.9.3: Upgrade to OS X 10.9.4 or later via Mac App Store > Updates, or download from support.apple.com.
  5. 5. After upgrade, verify fix by checking About This Mac shows version 10.9.4 or higher.
Caveat Upgrading from 10.8.x to 10.9.x may cause application incompatibility; some 32-bit apps not supported in 10.9+; ensure critical software is 64-bit compatible

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

Fix this in Mac Os X Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1376 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2014-1376 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