IpadosOperating system · Apple

CVE-2020-9785

HIGH · 7.8 CVSS v3.1 Published 2020-04-01
Fix available
A fix is available. Upgrade to 6.2 / 10.15.4 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Multiple memory corruption issues were addressed with improved state management. This issue is fixed in iOS 13.4 and iPadOS 13.4, macOS Catalina 10.15.4, tvOS 13.4, watchOS 6.2. A malicious 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 confidence

Memory corruption vulnerability in Apple kernel (IOKit) allowing a malicious application to execute arbitrary code with kernel privileges. Multiple issues addressed with improved state management.

MitigationApply Apple security updates: iOS 13.4+, iPadOS 13.4+, macOS Catalina 10.15.4+, tvOS 13.4+, watchOS 6.2+. Prioritize mobile devices and any system permitting third-party application installation.

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
IpadosOperating system
Affected:< 13.4
Iphone OsOperating system
Affected:< 13.4
Mac Os XOperating system
Affected:< 10.15.4
TvosOperating system
Affected:< 13.4
WatchosOperating system
Affected:< 6.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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

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

  1. Identify the Apple operating system
    On the device, go to Settings > General > About (iOS/iPadOS/watchOS/tvOS) or System Preferences > About (macOS) to see the product name
    Affected if The system runs any of iPadOS, iPhone OS, macOS X, tvOS, or watchOS
  2. Check the installed version number
    Note the version number shown in the About screen (e.g., 13.3.1 for iOS, 10.15.3 for macOS)
    Affected if The version cannot be determined or is below the fixed release for that product
  3. Compare iOS version to threshold
    If the device runs iPhone OS, verify whether the version is less than 13.4 (for example, 13.3, 13.3.1, etc.)
    Affected if iOS version is < 13.4
  4. Compare iPadOS version to threshold
    If the device runs iPadOS, verify whether the version is less than 13.4
    Affected if iPadOS version is < 13.4
  5. Compare macOS version to threshold
    If the system runs macOS X, verify whether the version is less than 10.15.4 (for example, 10.15.3, 10.15.2)
    Affected if macOS version is < 10.15.4
  6. Compare tvOS and watchOS versions
    For tvOS check if version < 13.4; for watchOS check if version < 6.2
    Affected if tvOS version is < 13.4 OR watchOS version is < 6.2

The system is affected if it runs any of the listed Apple operating systems at a version lower than the corresponding fixed release (iOS/iPadOS/tvOS < 13.4, watchOS < 6.2, macOS < 10.15.4).

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 6.2 / 10.15.4 / 13.4 or later
Fixed in 6.210.15.413.4
Interim mitigation

Apply Apple security updates: iOS 13.4+, iPadOS 13.4+, macOS Catalina 10.15.4+, tvOS 13.4+, watchOS 6.2+. Prioritize mobile devices and any system permitting third-party application installation.

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-9785 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