dbcve.org
Mac Os XOperating system · Apple

CVE-2016-7604

MEDIUM · 5.5 CVSS v3.0 Published 2017-02-20
Fix available
A fix is available. Upgrade to after 10.12.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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
An issue was discovered in certain Apple products. macOS before 10.12.2 is affected. The issue involves the "CoreCapture" component. It allows local users to cause a denial of service (NULL pointer dereference) 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 confidence

A NULL pointer dereference vulnerability in the CoreCapture component of macOS prior to 10.12.2 allows local authenticated users to cause a denial of service. The vulnerability triggers when certain unspecified vectors cause the component to dereference a NULL pointer, resulting in a system crash or service interruption.

MitigationApply the macOS 10.12.2 security update or later to patch the CoreCapture vulnerability. For systems that cannot be updated, consider isolating affected systems or implementing monitoring for crash reports indicating CoreCapture failures.

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.12.1

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checks

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

  1. Check installed macOS version
    Run 'sw_vers -productVersion' in Terminal or go to Apple menu > About This Mac
    Affected if Version is 10.12.1 or earlier (10.12.0 through 10.12.1)
  2. Verify CoreCapture component is present
    Check for the presence of '/System/Library/PrivateFrameworks/CoreCapture.framework' using Finder or 'ls -la' command in Terminal
    Affected if The CoreCapture framework exists on the system (it is a default component in affected macOS versions)
  3. Review system crash logs for CoreCapture failures
    Open Console.app and filter for 'CoreCapture' in crash logs, or check /Library/Logs/DiagnosticReports for crash reports mentioning 'CoreCapture'
    Affected if Crash reports exist showing CoreCapture-related kernel panics or service interruptions

A system is affected if it runs macOS 10.12.1 or earlier and contains the CoreCapture component, which is present by default in those versions.

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.

From vendor data
Upgrade available Upgrade to a release after 10.12.1
Interim mitigation

Apply the macOS 10.12.2 security update or later to patch the CoreCapture vulnerability. For systems that cannot be updated, consider isolating affected systems or implementing monitoring for crash reports indicating CoreCapture failures.

Fix this in Mac Os X Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-7604 — 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-2016-7604 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