CVE-2021-30740
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 logic issue was addressed with improved validation. This issue is fixed in macOS Big Sur 11.4, tvOS 14.6, watchOS 7.5, iOS 14.6 and iPadOS 14.6. A malicious 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 logic validation flaw in Apple operating systems allowed a locally planted malicious application to bypass security restrictions and execute code at the kernel (ring 0) privilege level. The vulnerability stemmed from inadequate validation checks in privileged code paths, enabling privilege escalation from userland to kernel mode.
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.6< 14.6>= 11.0.1, < 11.4< 14.6< 7.5CVSS 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.
-
Identify the operating system running on the Apple deviceDetermine whether the device runs macOS, iOS, iPadOS, tvOS, or watchOS. For macOS, use 'sw_vers' in Terminal. For iOS/iPadOS, go to Settings > General > About. For tvOS, go to Settings > General > About. For watchOS, open the Watch app on iPhone and go to General > About.Affected if The device runs any of the affected Apple operating systems.
-
Check the installed macOS versionRun 'sw_vers -productVersion' in Terminal or check System Preferences > About. Compare the version to the affected range: 11.0.1 through 11.3.x.Affected if The macOS version is 11.0.1, 11.1, 11.2, 11.3, or 11.3.x.
-
Check the installed iOS or iPadOS versionGo to Settings > General > About on the device and note the version number. Compare to the affected range: any version below 14.6.Affected if The iOS or iPadOS version is below 14.6 (e.g., 14.5, 14.4, 13.x, etc.).
-
Check the installed tvOS versionGo to Settings > General > About on the Apple TV and note the version number. Compare to the affected range: any version below 14.6.Affected if The tvOS version is below 14.6.
-
Check the installed watchOS versionOpen the Watch app on the paired iPhone, go to General > About, and note the watchOS version. Compare to the affected range: any version below 7.5.Affected if The watchOS version is below 7.5.
-
Determine if the device allows installation of untrusted applicationsOn iOS/iPadOS, go to Settings > General > VPN & Device Management (or Settings > Profiles & Device Management) to check for installed configuration profiles or enterprise apps. On macOS, check System Preferences > Security & Privacy for app installation restrictions.Affected if The device has any untrusted or enterprise applications installed, which could serve as the local planting vector for exploitation.
The device is affected if it runs any version within the affected ranges (macOS 11.0.1-11.3.x, iOS/iPadOS below 14.6, tvOS below 14.6, or watchOS below 7.5) and has the capability to run locally planted 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 · scoped7.511.414.6
Apply the vendor-supplied security updates for the affected Apple operating systems (macOS Big Sur 11.4+, tvOS 14.6+, watchOS 7.5+, iOS/iPadOS 14.6+) to resolve the logic validation issue. Avoid installing untrusted applications to reduce attack surface.
iOS 14.6, iPadOS 14.6, macOS Big Sur 11.4, tvOS 14.6, watchOS 7.5
- For iPhone and iPad: Go to Settings > General > Software Update and install iOS 14.6 / iPadOS 14.6
- For Mac: Go to System Preferences > Software Update and install macOS Big Sur 11.4
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 14.6
- For Apple Watch: On your iPhone, open the Watch app, go to General > Software Update and install watchOS 7.5
- Alternatively, for all devices, ensure automatic updates are enabled or manually download and install the latest firmware from Apple's support site
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-30740 — 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-30740 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