SafariWeb browser · Apple
CVE-2020-9800
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 type confusion issue was addressed with improved memory handling. This issue is fixed in iOS 13.5 and iPadOS 13.5, tvOS 13.4.5, watchOS 6.2.5, Safari 13.1.1, iTunes 12.10.7 for Windows, iCloud for Windows 11.2, iCloud for Windows 7.19. Processing maliciously crafted web content may lead to arbitrary code execution.
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 confidenceA type confusion vulnerability in WebKit allows processing of maliciously crafted web content to lead to arbitrary code execution. The fix involved improved memory handling to prevent the type confusion from being exploitable.
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
SafariWeb browser
< 13.1.1< 7.19>= 11.0, < 11.2< 12.10.7< 13.5< 13.5< 10.15.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Safari versionOpen Safari, click Safari in the menu bar, select About Safari. The version number appears next to the Safari logo.Affected if Version is below 13.1.1 (for macOS or Windows)
-
Check iTunes version (Windows)Open iTunes, click Help in the menu bar, select About iTunes. The version number is displayed in the dialog.Affected if Version is below 12.10.7
-
Check iCloud for Windows versionOpen iCloud, click the gear icon or Help menu, select About iCloud. The version number is displayed.Affected if Version is below 7.19, or between 11.0 and 11.2 (inclusive)
-
Check iOS version on iPhoneGo to Settings > General > About on the iPhone. The version number is shown next to 'Version'.Affected if Version is below 13.5
-
Check iPadOS version on iPadGo to Settings > General > About on the iPad. The version number is shown next to 'Version'.Affected if Version is below 13.5
-
Check macOS versionClick the Apple menu, select About This Mac. The version number is displayed below the macOS name.Affected if Version is below 10.15.5 (Catalina)
A user is affected if any WebKit-based Apple product (Safari, iTunes, iCloud, iOS, iPadOS, macOS, or watchOS) installed in their environment has a version number that falls within the affected ranges specified for that product.
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.57.1910.15.5
Update all affected Apple products (iOS, iPadOS, tvOS, watchOS, Safari, iTunes, and iCloud for Windows) to the patched versions specified in the advisory.
Fix this in Safari
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9800 — 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-9800 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