CVE-2020-10010
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 · uneditedA path handling issue was addressed with improved validation. This issue is fixed in macOS Big Sur 11.0.1, iOS 14.2 and iPadOS 14.2, tvOS 14.2, watchOS 7.1. A local attacker may be able to elevate their privileges.
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 path handling vulnerability in Apple operating systems allows a local attacker to elevate privileges to higher permission levels. The issue stems from insufficient validation of path inputs, likely allowing path traversal or manipulation to access protected resources.
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< 14.2< 14.2< 11.0.1>= 10.14, < 10.14.6>= 10.15, < 10.15.7= 10.14.6= 10.15.7< 14.2< 7.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check macOS version on Apple Mac computersRun 'sw_vers' in Terminal or go to Apple menu > About This Mac to view the macOS version numberAffected if Version is earlier than 10.14.6, or between 10.14.6 and 10.15.7, or earlier than 11.0.1 (for versions 10.14.x, 10.15.x)
-
Check iOS version on iPhoneGo to Settings > General > About on the device and note the version numberAffected if Version is earlier than 14.2
-
Check iPadOS version on iPadGo to Settings > General > About on the device and note the version numberAffected if Version is earlier than 14.2
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on Apple TV and note the tvOS build numberAffected if Version is earlier than 14.2
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone, go to My Watch > General > About and note the watchOS versionAffected if Version is earlier than 7.1
If the installed OS version matches any of the affected ranges (iOS/iPadOS < 14.2, macOS < 11.0.1 with specific 10.14.x/10.15.x conditions, tvOS < 14.2, or watchOS < 7.1), the environment is vulnerable to this path handling privilege escalation flaw.
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.
From vendor data7.110.14.610.15.7
Apply vendor-supplied updates: macOS Big Sur 11.0.1 or later, iOS/iPadOS 14.2 or later, tvOS 14.2 or later, watchOS 7.1 or later.
- Consultation2.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10010 — 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-2020-10010 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