Mac Os XOperating system · Apple

CVE-2021-30830

HIGH · 7.8 CVSS v3.1 Published 2021-10-19
Fix available
A fix is available. Upgrade to 11.6 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A memory corruption issue was addressed with improved memory handling. This issue is fixed in Security Update 2021-005 Catalina, macOS Big Sur 11.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 confidence

A memory corruption vulnerability in the macOS kernel (likely in IOKit/IORegistry framework) allows a malicious local application to execute arbitrary code with kernel-level privileges, achieving local privilege escalation. This is a use-after-free or similar memory handling flaw in kernel-space code.

MitigationApply Security Update 2021-005 for macOS Catalina or update to macOS Big Sur 11.6 or later to patch the kernel memory corruption. Alternatively, restrict execution of untrusted applications via Gatekeeper and disable or limit local user privileges.

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
Mac Os XOperating system
Affected:>= 10.15, <= 10.15.6= 10.15.7
macOSOperating system
Affected:>= 11.0, < 11.6

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed macOS version
    Run `sw_vers -productVersion` in Terminal or view System Preferences > About
    Affected if Version matches 10.15, 10.15.1, 10.15.2, 10.15.3, 10.15.4, 10.15.5, 10.15.6, 10.15.7, 11.0, 11.1, 11.2, 11.3, 11.4, or 11.5
  2. Confirm macOS release name
    Run `sw_vers -productVersion` and note whether the major version is 10.x (Catalina) or 11.x (Big Sur)
    Affected if Running macOS Catalina 10.15.x or macOS Big Sur 11.0-11.5
  3. Verify patch status
    Check System Preferences > Software Update for available security updates, or run `system_profiler SPSoftwareDataType` to view installed updates
    Affected if Security Update 2021-005 for Catalina is not installed, or macOS is not updated to 11.6 or later

A system is affected if it runs macOS Catalina 10.15.x (any subversion) or macOS Big Sur 11.0 through 11.5 and lacks the corresponding security patch.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.6 or later
Fixed in 11.6
Interim mitigation

Apply Security Update 2021-005 for macOS Catalina or update to macOS Big Sur 11.6 or later to patch the kernel memory corruption. Alternatively, restrict execution of untrusted applications via Gatekeeper and disable or limit local user privileges.

Recommended fix High confidence

macOS 10.15.7 with Security Update 2021-005 Catalina, or macOS Big Sur 11.6

  1. Check current macOS version by clicking Apple menu > About This Mac
  2. Back up important data using Time Machine or another backup method
  3. For macOS 10.15.x (Catalina): Install Security Update 2021-005 by opening System Preferences > Software Update, or download from Apple Support downloads
  4. For macOS 11.x (Big Sur): Upgrade to macOS Big Sur 11.6 by opening System Preferences > Software Update, or download from Apple Support downloads
  5. Restart the system after the update completes
  6. Verify the update was applied by checking About This Mac > System Report > Software > Installed Security Updates
Caveat Standard macOS upgrade considerations apply - ensure compatible applications and backup data before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mac Os X Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-30830 — 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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-30830 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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