CVE-2021-1788
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 use after free issue was addressed with improved memory management. This issue is fixed in macOS Big Sur 11.2, Security Update 2021-001 Catalina, Security Update 2021-001 Mojave, tvOS 14.4, watchOS 7.3, iOS 14.4 and iPadOS 14.4, Safari 14.0.3. 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 use-after-free vulnerability in WebKit (Apple's browser engine) affecting multiple Apple operating systems. When processing maliciously crafted web content, the browser may free memory while still holding a pointer to it, potentially allowing an attacker to execute arbitrary code by exploiting the dangling pointer.
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.0.3= 10.0= 33< 14.4< 14.4>= 10.14, < 10.14.6>= 10.15, < 10.15.7= 10.14.6= 10.15.7>= 11.0, < 11.2< 14.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 your operating systemDetermine if the system is running macOS, iOS, iPadOS, tvOS, Debian Linux, or Fedora. On Apple devices, go to Settings > General > About (iOS/iPadOS/tvOS) or Apple menu > About This Mac (macOS). On Linux, run 'uname -a' or check /etc/os-release.Affected if The OS is any of the affected platforms listed in the CVE (Safari < 14.0.3, iOS/iPadOS < 14.4, macOS < 11.2 or specific Catalina/Mojave versions, tvOS < 14.4, Debian 10, Fedora 33)
-
Check Safari version on macOSOpen Safari and go to Safari > About Safari. Note the version number displayed.Affected if Safari version is earlier than 14.0.3 on macOS or macOS X
-
Check iOS or iPadOS versionOpen Settings > General > About and note the version number.Affected if iOS or iPadOS version is earlier than 14.4
-
Check macOS versionOpen Apple menu > About This Mac. The version is displayed (e.g., 10.15.7, 11.1, 11.2).Affected if macOS version is 10.14.x (before 10.14.6), 10.15.x (before 10.15.7), or 11.0-11.1 (before 11.2)
-
Confirm WebKit usageIdentify if any application uses WebKit for rendering web content. On Apple platforms, Safari and many third-party browsers use WebKit. Check the browser or app info to confirm the rendering engine.Affected if A WebKit-based browser or application is in use on an affected OS version, as the vulnerability triggers when processing malicious web content
You are affected if your Safari version is below 14.0.3, or your iOS/iPadOS/tvOS is below 14.4, or your macOS falls within the vulnerable range (10.14.x before 10.14.6, 10.15.x before 10.15.7, or 11.0-11.1), and you use WebKit to browse the web.
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 · scoped10.14.610.15.711.2
Apply the relevant security updates: iOS 14.4/iPadOS 14.4 for mobile devices, macOS Big Sur 11.2 or Security Update 2021-001 for Catalina/Mojave, tvOS 14.4, watchOS 7.3, or Safari 14.0.3 depending on the affected platform.
macOS 11.2+, Security Update 2021-001 for Catalina/Mojave, iOS/iPadOS 14.4+, tvOS 14.4+, Safari 14.0.3
- For macOS Big Sur (11.x): Update to macOS 11.2 or later via System Preferences > Software Update
- For macOS Catalina (10.15): Apply Security Update 2021-001 via System Preferences > Software Update
- For macOS Mojave (10.14): Apply Security Update 2021-001 via System Preferences > Software Update
- For iPhone/iPad: Update to iOS/iPadOS 14.4 or later via Settings > General > Software Update
- For tvOS: Update to tvOS 14.4 or later via Settings > System > Software Update
- For Safari: Update Safari by installing the corresponding macOS/iOS/iPadOS update (Safari 14.0.3 is included in the above updates)
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-2021-1788 — 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-1788 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