CVE-2021-30881
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 input validation issue was addressed with improved memory handling. This issue is fixed in iOS 15.1 and iPadOS 15.1, macOS Monterey 12.0.1, tvOS 15.1, watchOS 8.1, Security Update 2021-007 Catalina, macOS Big Sur 11.6.1. Unpacking a maliciously crafted archive may lead to arbitrary code execution.
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 memory handling vulnerability in archive unpacking functionality allows arbitrary code execution when a user unpacks a maliciously crafted archive file. The issue was addressed through improved input validation and proper memory management during archive processing.
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< 15.1< 15.1< 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.
-
Identify your Apple device typeDetermine whether the device is an iPhone, iPad, Mac, Apple TV, or Apple Watch. On iPhone/iPad: check the model name in Settings > General > About. On Mac: check Apple menu > About This Mac. On Apple TV: check Settings > General > About. On Apple Watch: check the model on the watch or via the Watch app on paired iPhone.Affected if Device is any Apple product (iPhone, iPad, Mac, Apple TV, Apple Watch)
-
Check the installed iOS or iPadOS versionOn iPhone or iPad, go to Settings > General > About and note the Version number (for example, 15.0 or 14.7.1).Affected if iOS or iPadOS version is lower than 15.1
-
Check the installed macOS versionOn Mac, click Apple menu > About This Mac and note the macOS version (for example, 12.0, 11.5, or 10.15.7). Compare against the affected ranges: Catalina (10.15.7 or earlier), Big Sur (11.0 to 11.6.0), or Monterey (12.0).Affected if macOS version is 10.15.7 or earlier, between 11.0 and 11.6.0 inclusive, or exactly 12.0
-
Check the installed tvOS or watchOS versionOn Apple TV: go to Settings > General > About > Version. On Apple Watch: open the Watch app on paired iPhone, go to My Watch > General > About, and note the watchOS version.Affected if tvOS version is lower than 15.1 or watchOS version is lower than 8.1
You are affected if your Apple device runs iOS/iPadOS, macOS, tvOS, or watchOS versions lower than the fixed releases (iOS 15.1, iPadOS 15.1, macOS 11.6.1/12.0.1/10.15.7 update, tvOS 15.1, or watchOS 8.1).
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 applicable Apple security update (iOS 15.1, iPadOS 15.1, macOS Monterey 12.0.1/Big Sur 11.6.1/Catalina Security Update 2021-007, tvOS 15.1, or watchOS 8.1) to all affected devices and systems.
iOS 15.1 / iPadOS 15.1 / macOS Monterey 12.0.1 / tvOS 15.1 / watchOS 8.1 / Security Update 2021-007 Catalina / macOS Big Sur 11.6.1
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 15.1 or later
- For macOS Big Sur (11.x): Go to System Preferences > Software Update and install macOS Big Sur 11.6.1
- For macOS Monterey (12.0): Go to System Preferences > Software Update and install macOS Monterey 12.0.1
- For macOS Catalina (10.15.7): Install Security Update 2021-007 Catalina via System Preferences > Software Update
- For tvOS: Go to Settings > System > Software Updates and install tvOS 15.1 or later
- For watchOS: On iPhone, open Watch app, go to My Watch > General > Software Update and install watchOS 8.1 or later
- Alternatively, manually download the latest IPSW firmware from https://developer.apple.com/download/ and restore via Finder or Xcode
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-30881 — 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-30881 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