CVE-2021-1817
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 corruption issue was addressed with improved state management. This issue is fixed in macOS Big Sur 11.3, iOS 14.5 and iPadOS 14.5, watchOS 7.4, tvOS 14.5. 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 confidenceThis is a memory corruption vulnerability in WebKit (Apple's browser engine) affecting macOS Big Sur, iOS/iPadOS, watchOS, and tvOS. The vulnerability allows arbitrary code execution when a user processes maliciously crafted web content. The fix involved improved state management to prevent the memory corruption.
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.5< 14.5>= 11.0, < 11.3< 14.5< 7.4CVSS 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.
-
Identify the Apple device and operating system typeDetermine whether the system is macOS, iOS, iPadOS, watchOS, or tvOS. On macOS, run 'sw_vers' or check System Preferences > About. On mobile devices, check Settings > General > About.Affected if The device runs any of the affected Apple operating systems listed in the CVE.
-
Check the installed macOS versionRun 'sw_vers -productVersion' in Terminal on macOS, or view System Preferences > About. Look for version numbers like 11.0, 11.1, 11.2, or 11.2.x.Affected if The macOS version is 11.0, 11.1, 11.2, or 11.2.x (versions 11.0 through 11.2.x are affected; 11.3 and later are fixed).
-
Check the installed iOS or iPadOS versionOpen Settings > General > About on the iPhone or iPad. Note the version number displayed (for example, 14.4, 14.4.1, 14.4.2).Affected if The iOS or iPadOS version is below 14.5 (versions 14.0 through 14.4.x are affected).
-
Check the installed watchOS or tvOS versionOn Apple Watch, open the Watch app on iPhone > My Watch > General > About, or go to Settings > General > About on the watch itself. On Apple TV, go to Settings > General > About.Affected if The watchOS version is below 7.4 or the tvOS version is below 14.5.
-
Confirm WebKit is in useVerify that Safari or any third-party browser/app that uses the WebKit rendering engine is being used. WebKit is the default engine for Safari and many apps on Apple platforms.Affected if The device runs an affected OS version AND processes untrusted web content through Safari or any WebKit-based application.
The environment is affected if any Apple device runs macOS 11.0-11.2.x, iOS/iPadOS below 14.5, watchOS below 7.4, or tvOS below 14.5, and the WebKit browser engine is used to process web content.
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 · scoped7.411.314.5
Apply the vendor-supplied patches by updating affected devices to macOS Big Sur 11.3+, iOS/iPadOS 14.5+, watchOS 7.4+, or tvOS 14.5+. Organizations should deploy these updates through their MDM or patch management infrastructure.
Upgrade to iOS 14.5 / iPadOS 14.5 / macOS Big Sur 11.3 / tvOS 14.5 / watchOS 7.4 as appropriate for your device
- For iOS devices: Go to Settings > General > Software Update, then download and install iOS 14.5
- For iPadOS devices: Go to Settings > General > Software Update, then download and install iPadOS 14.5
- For macOS devices: Open System Preferences > Software Update, or go to the Apple menu > System Preferences > Software Update, then download and install macOS Big Sur 11.3
- For tvOS devices: Go to Settings > System > Software Updates > Update Software, then download and install tvOS 14.5
- For watchOS devices: On the iPhone, open the Watch app, go to My Watch > General > Software Update, then download and install watchOS 7.4
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1817 — 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-2021-1817 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