CVE-2020-9827
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 denial of service issue was addressed with improved input validation. This issue is fixed in iOS 13.5 and iPadOS 13.5, macOS Catalina 10.15.5, tvOS 13.4.5, watchOS 6.2.5. A remote attacker may be able to cause a denial of service.
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 remote denial of service vulnerability in Apple operating systems (iOS, iPadOS, macOS, tvOS, watchOS) was addressed with improved input validation. A remote attacker could cause a denial of service by sending specially crafted input to the affected device.
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< 13.5< 10.15.5< 13.4.5< 6.2.5CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Apple device type and operating systemDetermine whether the device is an iPhone, iPad, Mac, Apple TV, or Apple Watch. This can be done via system settings on the device or device management consoles for enterprise environments.Affected if The device runs any of the affected Apple operating systems (iOS, iPadOS, macOS, tvOS, watchOS)
-
Check the installed iOS or iPadOS versionOn the device, go to Settings > General > About and note the version number. For bulk checking, use mobile device management (MDM) tools or Apple Configurator to query device OS versions.Affected if The version is below 13.5 on iPhone or iPad devices
-
Check the installed macOS versionClick the Apple menu > About This Mac. The version number appears below the macOS name. For remote checking, use commands like 'sw_vers' in Terminal or query via MDM/enterprise management tools.Affected if The version is below 10.15.5 on Mac computers
-
Check the installed tvOS versionGo to Settings > General > About > Version on Apple TV. For managed devices, query via MDM or Apple School/Business Manager.Affected if The version is below 13.4.5 on Apple TV devices
-
Check the installed watchOS versionOn Apple Watch, go to Settings > General > About and view the version. On the paired iPhone, open the Watch app > General > About. For enterprise deployment, query via MDM.Affected if The version is below 6.2.5 on Apple Watch devices
-
Assess network exposure of affected devicesReview network access controls and firewall rules to determine if these devices are reachable from untrusted networks. This vulnerability can be exploited remotely, so devices with direct internet exposure or accessible from less-trusted network segments are at higher risk.Affected if The device is network-accessible from external or untrusted networks in addition to being on an affected version
A user is affected if any Apple device on their network (iPhone, iPad, Mac, Apple TV, or Apple Watch) runs an OS version below the thresholds (iOS/iPadOS 13.5, macOS 10.15.5, tvOS 13.4.5, watchOS 6.2.5) and is reachable over the network.
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 data6.2.510.15.513.4.5
Update affected Apple devices to iOS 13.5/iPadOS 13.5, macOS Catalina 10.15.5, tvOS 13.4.5, or watchOS 6.2.5 or later versions.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9827 — 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-9827 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