CVE-2021-30889
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 buffer overflow issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.0.1, iOS 15.1 and iPadOS 15.1, watchOS 8.1, tvOS 15.1. 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 buffer overflow vulnerability in WebKit allows arbitrary code execution when processing maliciously crafted web content. The issue was addressed with improved memory handling in the affected Apple operating systems.
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< 15.1< 15.1< 12.0.1< 15.1< 8.1CVSS 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 Apple device typeDetermine whether the device is an iPhone, iPad, Mac, Apple Watch, or Apple TV. This matters because different OS version ranges apply to different device categories.Affected if Device is an iPhone, iPad, Mac, Apple Watch, or Apple TV running an affected OS version
-
Check iOS or iPadOS versionOn iPhone or iPad, go to Settings > General > About. Note the version number displayed next to 'Version'. Compare it to 15.1 - any version below 15.1 is affected.Affected if iOS or iPadOS version is below 15.1
-
Check macOS versionOn Mac, click the Apple menu > About This Mac. Note the version number (such as 12.0, 11.x, etc.). Compare it to 12.0.1 - any version below 12.0.1 is affected.Affected if macOS version is below 12.0.1
-
Check watchOS versionOn Apple Watch, open the Settings app > General > About. Note the version. Or check via paired iPhone in Watch app > My Watch > About. Compare to 8.1 - any version below 8.1 is affected.Affected if watchOS version is below 8.1
-
Check tvOS versionOn Apple TV, go to Settings > General > About TV. Note the version number. Compare to 15.1 - any version below 15.1 is affected.Affected if tvOS version is below 15.1
-
Confirm WebKit is in useThis vulnerability affects any app using WebKit on affected devices. Safari uses WebKit by default. Third-party browsers on iOS/iPadOS also use WebKit due to platform restrictions. Check if Safari or any WebKit-based browser is installed and used.Affected if Safari or any WebKit-based browser is used on a device with an affected OS version
A device is affected if it is an Apple device (iPhone, iPad, Mac, Apple Watch, or Apple TV) running an OS version below the fixed release (iOS/iPadOS/tvOS/watchOS 15.1 or macOS 12.0.1) and uses WebKit to render 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 · scoped8.112.0.115.1
Apply the security updates (iOS 15.1 and later, iPadOS 15.1 and later, watchOS 8.1 and later, tvOS 15.1 and later, macOS Monterey 12.0.1 and later) to all affected devices.
iOS 15.1+, iPadOS 15.1+, macOS Monterey 12.0.1+, watchOS 8.1+, tvOS 15.1+
- Identify the affected Apple device (iPhone, iPad, Mac, Apple Watch, or Apple TV)
- Determine the current installed OS version in Settings > General > About
- For iPhone/iPad: Go to Settings > General > Software Update and upgrade to iOS/iPadOS 15.1 or later
- For Mac: Go to System Preferences > Software Update and upgrade to macOS Monterey 12.0.1 or later
- For Apple Watch: Open the Watch app on iPhone, go to General > Software Update, and upgrade to watchOS 8.1 or later
- For Apple TV: Go to Settings > System > Software Updates and upgrade to tvOS 15.1 or later
- After upgrading, verify the new OS version is installed and confirm the vulnerability is patched
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-30889 — 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-30889 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