CVE-2021-30858
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.8 and iPadOS 14.8, macOS Big Sur 11.6. Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited.
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 allows processing of maliciously crafted web content to trigger memory corruption leading to arbitrary code execution. This is a memory management flaw that can be exploited remotely without user interaction beyond visiting a malicious webpage.
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= 33= 34= 10.0= 11.0>= 13.1, < 14.8< 12.5.5>= 13.0, < 14.8< 11.6CVSS 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 operating system and productDetermine if the device runs Apple iOS, iPadOS, macOS, Fedora, or Debian Linux, as these are the affected products listed for this CVEAffected if The device runs any of the listed affected operating systems or Linux distributions
-
Check iOS or iPadOS version on Apple mobile devicesOn iPhone or iPad, go to Settings > General > About to view the version number. Compare against the affected ranges: iOS < 12.5.5 OR >= 13.0 and < 14.8; iPadOS >= 13.1 and < 14.8Affected if The iOS version is less than 12.5.5, or is 13.x through 14.7.x; OR the iPadOS version is 13.1 through 14.7.x
-
Check macOS version on Apple computersClick the Apple menu > About This Mac to view the macOS version. Compare against affected range: macOS < 11.6 (any version before Big Sur 11.6)Affected if The macOS version is 11.5.x or earlier, or any version of Catalina (10.15.x) or earlier
-
Check for WebKitGTK on Fedora or Debian LinuxOn Fedora, run: rpm -qa | grep -i webkit. On Debian, run: dpkg -l | grep -i webkit. This checks if the WebKit rendering engine package is installedAffected if WebKitGTK package is installed on Fedora 33 or 34, or Debian 10.0 or 11.0, and the package version is unpatched
-
Verify if Safari or any app uses WebKit for web contentOn macOS/iOS, confirm Safari is used or check if third-party apps embed WebView components that render web content. On Linux, check if applications use webkit2gtk (such as GNOME Web, evolution, or other GTK webviews)Affected if Safari or any WebKit-based application processes untrusted web content on a vulnerable OS version
A defender is affected if their iOS/iPadOS device runs a version before 14.8, their macOS device runs a version before 11.6, or their Fedora/Debian system has an unpatched WebKitGTK package installed, AND they process untrusted web content through Safari or a WebKit-based application.
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 · scoped11.612.5.514.8
Apply the available security updates: iOS 14.8 and later, iPadOS 14.8 and later, or macOS Big Sur 11.6 and later. Prioritize patching given active exploitation in the wild.
iOS 14.8+, iPadOS 14.8+, macOS Big Sur 11.6+
- For iOS devices: Go to Settings > General > Software Update and upgrade to iOS 14.8 or later
- For iPadOS devices: Go to Settings > General > Software Update and upgrade to iPadOS 14.8 or later
- For macOS devices: Go to System Preferences > Software Update and upgrade to macOS Big Sur 11.6 or later
- After updating, verify the version in Settings/About to confirm the update was applied
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-30858 — 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 sources- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- support.apple.com
- support.apple.com
- support.apple.com
- www.debian.org
- www.debian.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.cisa.gov
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-30858 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