CVE-2021-30909
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 memory handling. This issue is fixed in iOS 15.1 and iPadOS 15.1, macOS Monterey 12.0.1, iOS 14.8.1 and iPadOS 14.8.1, tvOS 15.1, watchOS 8.1, Security Update 2021-007 Catalina, macOS Big Sur 11.6.1. An application may be able to execute arbitrary code with kernel privileges.
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 · moderate confidenceA memory corruption vulnerability in Apple's kernel allows a malicious application to escalate privileges and execute arbitrary code with kernel-level access. This is a local privilege escalation issue affecting multiple Apple operating systems, requiring the attacker to first run code on the target device.
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.8.1= 15.0< 14.8.1= 15.0< 10.15.7= 10.15.7>= 11.0, < 11.6.1= 12.0< 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Check iOS or iPadOS versionOn the device, go to Settings > General > About and note the Version number, or run 'sw_vers -productVersion' via terminal if you have remote accessAffected if The version is less than 14.8.1, or exactly 15.0
-
Check macOS versionRun 'sw_vers -productVersion' in Terminal, or click Apple menu > About This MacAffected if The version is 10.15.7 (any build), or 11.x before 11.6.1, or exactly 12.0
-
Check tvOS versionOn Apple TV, go to Settings > General > About and note the version numberAffected if The version is less than 15.1
-
Check watchOS versionOn Apple Watch, open the Watch app on paired iPhone, go to My Watch > General > About and note the versionAffected if The version is less than 8.1
-
Confirm kernel-level code execution capabilityThis is a local privilege escalation requiring pre-existing code execution. Verify whether untrusted third-party applications can run on the device (not applicable to standard user scenarios)Affected if A malicious application with code execution capability is already running on the affected OS version
The device is affected if it runs any iOS/iPadOS < 14.8.1 or = 15.0, macOS 10.15.7, macOS 11.x < 11.6.1 or = 12.0, tvOS < 15.1, or watchOS < 8.1, and a malicious application already has code execution on it.
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.110.15.711.6.1
Apply the available security updates (iOS 15.1/14.8.1, macOS Monterey 12.0.1/Big Sur 11.6.1/Catalina Security Update 2021-007, tvOS 15.1, watchOS 8.1) to patched versions.
iOS 14.8.1/iPadOS 14.8.1 or iOS 15.1/iPadOS 15.1; macOS Security Update 2021-007 (Catalina), macOS Big Sur 11.6.1+, macOS Monterey 12.0.1+; tvOS 15.1+; watchOS 8.1+
- For iPhone/iPad: Upgrade to iOS 14.8.1 or iPadOS 14.8.1 (or iOS 15.1/iPadOS 15.1 if available for your device) via Settings > General > Software Update
- For macOS Catalina (10.15.7): Install Security Update 2021-007 via System Preferences > Software Update
- For macOS Big Sur (11.x): Upgrade to macOS Big Sur 11.6.1 or later via System Preferences > Software Update
- For macOS Monterey (12.0): Upgrade to macOS Monterey 12.0.1 or later via System Preferences > Software Update
- For tvOS: Upgrade to tvOS 15.1 or later via Settings > System > Software Updates
- For watchOS: Upgrade to watchOS 8.1 or later via the Watch app on iPhone
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-30909 — 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-30909 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