CVE-2021-30802
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 iOS 14.7, tvOS 14.7. 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 use-after-free vulnerability in WebKit (the browser engine used by Safari on iOS and tvOS) allows arbitrary code execution when processing maliciously crafted web content. The vulnerability stems from improper memory management where a pointer is accessed after its memory has been freed.
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.7< 14.7CVSS 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 device typeDetermine if the device is an iPhone, iPad, or Apple TV. On iOS devices, go to Settings > General > About > Model Name. On tvOS, go to Settings > General > About > Model.Affected if Device is an iPhone, iPad, or Apple TV running iOS/tvOS
-
Check iOS version on iPhone or iPadOpen Settings > General > About > Version. Note the version number displayed (for example, 14.6 or 14.7).Affected if iOS version is lower than 14.7 (for example, 14.6, 14.5, or earlier)
-
Check tvOS version on Apple TVOpen Settings > General > About > Version. Note the version number displayed (for example, 14.6 or 14.7).Affected if tvOS version is lower than 14.7 (for example, 14.6, 14.5, or earlier)
-
Confirm WebKit exposureVerify that Safari or any app using WebKit is enabled and used on the device. This CVE is triggered through malicious web content processed by WebKit.Affected if WebKit-based browser or apps are actively used on a vulnerable iOS/tvOS version
A device is affected if it is an iPhone, iPad, or Apple TV running iOS or tvOS version lower than 14.7, and the user browses web content using Safari or WebKit-based applications.
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 · scoped14.7
Apply iOS 14.7/tvOS 14.7 or later security updates to affected devices. Avoid browsing untrusted websites until patches are deployed.
iOS 14.7 and tvOS 14.7
- Back up your iOS device to iCloud or your computer before updating
- Connect your iPhone/iPad to Wi-Fi and ensure it has at least 50% battery or is plugged into power
- On your iOS device, go to Settings > General > Software Update
- Download and install iOS 14.7 when it appears
- For Apple TV users: Go to Settings > System > Software Updates > Update Software and install tvOS 14.7
- After updating, verify the version by checking Settings > General > About > Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30802 — 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-30802 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