CVE-2020-9859
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 memory consumption issue was addressed with improved memory handling. This issue is fixed in iOS 13.5.1 and iPadOS 13.5.1, macOS Catalina 10.15.5 Supplemental Update, tvOS 13.4.6, watchOS 6.2.6. An application may be able to execute arbitrary code with kernel 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 · high confidenceThis is a kernel-level memory consumption vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, watchOS). A malicious local application could exploit improper memory handling to execute arbitrary code with kernel/root privileges, achieving full device compromise.
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< 13.5.1< 13.5.1< 10.15.5< 13.4.6< 6.2.6CVSS 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 iOS version on iPhone or iPadOpen Settings > General > About > Version. Note the build number and version (e.g., 13.5 or earlier).Affected if The version shown is earlier than 13.5.1 (or the build number is below the security update build)
-
Check macOS versionClick the Apple menu > About This Mac. Look at the macOS version number displayed.Affected if The version is earlier than 10.15.5 (or the build number is older than the Catalina 10.15.5 Supplemental Update)
-
Check tvOS versionOpen Settings > General > About > Version on the Apple TV device.Affected if The version is earlier than 13.4.6
-
Check watchOS versionOpen the Watch app on paired iPhone, go to General > About, or check directly on Apple Watch via Settings > General > About.Affected if The version is earlier than 6.2.6
-
Determine if device allows third-party app installationOn iOS/iPadOS: go to Settings > General > Device Management (or Profiles & Device Management). On macOS: check System Preferences > Security & General for app installation restrictions.Affected if Unrestricted app installation from unknown developers is allowed (this is a precondition for a malicious local app to be installed and exploit this kernel flaw)
The device is affected if the installed OS version is below 13.5.1 for iOS/iPadOS, below 10.15.5 for macOS, below 13.4.6 for tvOS, or below 6.2.6 for watchOS, AND the device permits installation of third-party applications.
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 · scoped6.2.610.15.513.4.6
Apply the vendor-supplied security updates: iOS 13.5.1, iPadOS 13.5.1, macOS Catalina 10.15.5 Supplemental Update, tvOS 13.4.6, or watchOS 6.2.6 and later versions to all affected devices.
iOS 13.5.1/iPadOS 13.5.1, macOS Catalina 10.15.5 Supplemental Update, tvOS 13.4.6, or watchOS 6.2.6 (depending on device)
- Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, or Apple Watch)
- Check the current OS version on the device (Settings > General > About on iOS/iPadOS, System Preferences > About on macOS, Settings > General > About on tvOS, Settings > General on watchOS)
- Create a backup of important data before updating
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 13.5.1 or iPadOS 13.5.1
- For Mac: Go to System Preferences > Software Update and install macOS Catalina 10.15.5 Supplemental Update, or download from Apple Support
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 13.4.6
- For Apple Watch: On the iPhone, open the Watch app, go to General > Software Update and install watchOS 6.2.6
- Verify the update was successful by checking the OS version again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9859 — 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-9859 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