CVE-2021-30780
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 · uneditedAn out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 14.7, macOS Big Sur 11.5, watchOS 7.6, tvOS 14.7, Security Update 2021-005 Mojave, Security Update 2021-004 Catalina. A malicious application may be able to gain root 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 · high confidenceAn out-of-bounds write vulnerability in Apple's core operating systems (iOS, macOS, watchOS, tvOS) allows a malicious application to write data beyond allocated memory boundaries. This memory corruption flaw enables local privilege escalation, potentially granting the attacker root/system-level 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< 14.7>= 10.14, <= 10.14.5>= 10.15, <= 10.15.6= 10.14.6= 10.15.7>= 11.0, < 11.5< 14.7< 7.6CVSS 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 version on iPhone or iPadGo to Settings > General > About > Version, or run 'sw_vers' via Terminal on a Mac with Finder sync enabled for iOS devicesAffected if Version is lower than 14.7 (for example, 14.6.x or earlier)
-
Check macOS versionGo to Apple menu > About This Mac > Version, or run 'sw_vers' in TerminalAffected if Version is 10.14.6, 10.14.5 or earlier, 10.15.7, 10.15.6 or earlier, or between 11.0 and 11.4.x (anything less than 11.5)
-
Check tvOS versionGo to Settings > General > About > Version on Apple TV, or check via Xcode device managementAffected if Version is lower than 14.7
-
Check watchOS versionOpen the Watch app on iPhone, go to General > About, or check via the Watch app settingsAffected if Version is lower than 7.6
If any Apple device runs an OS version that falls within the affected ranges (iOS < 14.7, macOS 10.14.x through 10.15.7 or 11.0-11.4.x, tvOS < 14.7, watchOS < 7.6), the environment is potentially affected by this privilege escalation vulnerability.
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.611.514.7
Apply the available Apple security updates (iOS 14.7+, macOS Big Sur 11.5+, watchOS 7.6+, tvOS 14.7+, Security Update 2021-005/2021-004) to all affected devices. Restrict application installation to trusted sources and use endpoint detection to identify suspicious applications.
iOS 14.7+, macOS Big Sur 11.5+, watchOS 7.6+, tvOS 14.7+, Security Update 2021-004/2021-005 for older macOS
- Check current iOS version: Settings > General > About > Version
- Check current macOS version: Apple menu > About This Mac
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 14.7 or later
- For macOS Big Sur (11.x): Go to System Preferences > Software Update and install macOS 11.5 or later
- For macOS Catalina (10.15): Install Security Update 2021-004 Catalina via System Preferences > Software Update
- For macOS Mojave (10.14): Install Security Update 2021-005 Mojave via System Preferences > Software Update
- For Apple Watch: Go to Settings > General > Software Update and install watchOS 7.6 or later
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 14.7 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30780 — 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-30780 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