CVE-2021-30677
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 · uneditedThis issue was addressed with improved environment sanitization. This issue is fixed in tvOS 14.6, iOS 14.6 and iPadOS 14.6, Security Update 2021-004 Catalina, Security Update 2021-005 Mojave, macOS Big Sur 11.4, watchOS 7.5. A malicious application may be able to break out of its sandbox.
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 sandbox escape vulnerability in multiple Apple operating systems (iOS, iPadOS, tvOS, macOS, watchOS) that allows a malicious local application to break out of its sandbox containment due to improper environment sanitization. This is a privilege escalation issue enabling code execution outside the intended sandbox boundary.
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>= 10.14, <= 10.14.5>= 10.15, <= 10.15.6= 10.14.6= 10.15.7>= 11.0, < 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 installed operating systemOn macOS, go to Apple menu > About This Mac to see the version number. On iOS/iPadOS, go to Settings > General > About. On tvOS, go to Settings > General > About. On watchOS, go to Settings > General > About.Affected if Any Apple device running an unpatched OS version.
-
Determine the exact macOS version numberOpen Terminal and run 'sw_vers' or 'system_profiler SPSoftwareDataType' to get the precise macOS build version (e.g., 10.15.7, 11.3.1).Affected if Running macOS with a version that falls within the affected ranges.
-
Check if macOS is in the affected Big Sur rangeIf running macOS 11.x (Big Sur), verify the version is lower than 11.4. The About This Mac window shows the major version (e.g., 11.3).Affected if macOS Big Sur versions 11.0 through 11.3.x are affected.
-
Check if macOS is in the affected Catalina rangeIf running macOS 10.15 (Catalina), verify the version is 10.15.7 or between 10.15 and 10.15.6.Affected if macOS Catalina versions 10.15, 10.15.1, 10.15.2, 10.15.3, 10.15.4, 10.15.5, 10.15.6, or 10.15.7 are affected.
-
Check if macOS is in the affected Mojave rangeIf running macOS 10.14 (Mojave), verify the version is 10.14.6 or between 10.14 and 10.14.5.Affected if macOS Mojave versions 10.14, 10.14.1, 10.14.2, 10.14.3, 10.14.4, 10.14.5, or 10.14.6 are affected.
-
Check iOS, iPadOS, tvOS, or watchOS versionOn iOS/iPadOS, go to Settings > General > About to see the version (e.g., 14.5). On Apple TV, go to Settings > General > About. On Apple Watch, go to Settings > General > About.Affected if iOS or iPadOS versions lower than 14.6, tvOS versions lower than 14.6, or watchOS versions lower than 7.5 are affected.
A device is affected if it runs any macOS version in the specified Catalina, Mojave, or Big Sur ranges, or runs iOS/iPadOS, tvOS, or watchOS versions below 14.6, 14.6, and 7.5 respectively.
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 available vendor patches: iOS 14.6, iPadOS 14.6, tvOS 14.6, macOS Big Sur 11.4, watchOS 7.5, Security Update 2021-004 (Catalina), and Security Update 2021-005 (Mojave) to all affected devices.
iOS 14.6 / iPadOS 14.6 / tvOS 14.6 / watchOS 7.5 / macOS Big Sur 11.4 / Security Update 2021-004 Catalina / Security Update 2021-005 Mojave
- Identify the device type (iPhone, iPad, Mac, Apple TV, or Apple Watch)
- Check the current OS version on the device
- For iPhone or iPad: Upgrade to iOS 14.6 or iPadOS 14.6
- For Mac: Upgrade to macOS Big Sur 11.4, or apply Security Update 2021-004 Catalina or Security Update 2021-005 Mojave as appropriate
- For Apple TV: Upgrade to tvOS 14.6
- For Apple Watch: Upgrade to watchOS 7.5
- Verify the upgrade was successful by checking the OS version again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30677 — 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-30677 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