dbcve.org
Mac Os XOperating system · Apple

CVE-2020-10007

MEDIUM · 5.5 CVSS v3.1 Published 2020-12-08
Fix available
A fix is available. Upgrade to 10.14.6 / 10.15.7 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
A logic issue was addressed with improved state management. This issue is fixed in macOS Big Sur 11.0.1. A malicious application may be able to determine kernel memory layout.

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 logic error in macOS kernel state management allows a malicious local application to determine kernel memory layout. This information disclosure vulnerability could aid attackers in bypassing kernel address space layout randomization (KASLR) as part of a larger exploit chain.

MitigationApply macOS Big Sur 11.0.1 or later to patch the kernel. This is a platform-level vulnerability requiring OS updates rather than application code changes.

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:< 11.0.1>= 10.14, < 10.14.6>= 10.15, < 10.15.7= 10.14.6= 10.15.7

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 view About This Mac
    Affected if The version returned is earlier than 11.0.1 (e.g., 10.14.6, 10.15.7, 10.15.6, 10.15.5, etc.)
  2. Confirm specific affected series
    Check if the version matches any of these: 10.14.x (any 10.14 release), 10.15.x (any 10.15 release), or any version < 11.0.1
    Affected if The version is in the 10.14.x or 10.15.x series, or is less than 11.0.1
  3. Verify build corresponds to affected release
    Run 'sw_vers -buildVersion' and cross-reference with Apple release notes for that macOS point release
    Affected if The build matches an unpatched version of macOS Mojave (10.14) or Catalina (10.15)

The environment is affected if it runs any macOS version before 11.0.1, specifically including 10.14.6 and 10.15.7 and all earlier 10.14.x and 10.15.x releases.

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 10.14.6 / 10.15.7 / 11.0.1 or later
Fixed in 10.14.610.15.711.0.1
Interim mitigation

Apply macOS Big Sur 11.0.1 or later to patch the kernel. This is a platform-level vulnerability requiring OS updates rather than application code changes.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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