CVE-2021-1882
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 memory corruption issue was addressed with improved validation. This issue is fixed in Security Update 2021-002 Catalina, iOS 14.5 and iPadOS 14.5, watchOS 7.4, tvOS 14.5, macOS Big Sur 11.3. An application may be able to gain elevated 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 memory corruption vulnerability in multiple Apple operating systems (iOS, iPadOS, watchOS, tvOS, macOS) that allowed a malicious application to gain elevated privileges through improper memory validation. The issue was addressed by implementing improved validation checks.
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.5< 14.5>= 10.15, <= 10.15.5= 10.15.6= 10.15.7>= 11.0, < 11.3< 14.5< 7.4CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 device and Apple operating systemDetermine whether the device is running iOS, iPadOS, watchOS, tvOS, or macOS. For macOS, open Terminal and run: sw_vers -productVersionAffected if The OS version matches one of the affected product ranges listed below
-
Check iOS or iPadOS version on mobile devicesGo to Settings > General > About > Version. Compare the displayed version number to the affected range: iOS < 14.5 or iPadOS < 14.5Affected if The installed iOS version is less than 14.5, or the installed iPadOS version is less than 14.5
-
Check macOS Catalina (10.15.x) versionRun 'sw_vers -productVersion' in Terminal. Affected versions are 10.15, 10.15.1, 10.15.2, 10.15.3, 10.15.4, 10.15.5, 10.15.6, or 10.15.7Affected if The macOS version is any release of 10.15.x (Catalina) including 10.15, 10.15.6, or 10.15.7
-
Check macOS Big Sur (11.x) versionRun 'sw_vers -productVersion' in Terminal. The affected range is macOS 11.0 through 11.2.x (any version less than 11.3)Affected if The macOS version is 11.0, 11.1, or 11.2 (any version 11.x less than 11.3)
-
Check watchOS or tvOS version on Apple TV or Apple WatchOn Apple Watch: open the Watch app on paired iPhone > General > About. On Apple TV: go to Settings > General > About. Compare to affected ranges: watchOS < 7.4 or tvOS < 14.5Affected if The watchOS version is less than 7.4, or the tvOS version is less than 14.5
The environment is affected if any Apple device runs an OS version that falls within the vulnerable ranges: iOS/iPadOS < 14.5, watchOS < 7.4, tvOS < 14.5, macOS Catalina (10.15.x), or macOS Big Sur 11.0-11.2.x.
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.411.314.5
Apply the relevant security updates: iOS 14.5 and later, iPadOS 14.5 and later, watchOS 7.4 and later, tvOS 14.5 and later, macOS Big Sur 11.3 and later, or Security Update 2021-002 for Catalina.
iOS 14.5/iPadOS 14.5, macOS 11.3, watchOS 7.4, tvOS 14.5, or Security Update 2021-002 for macOS 10.15 Catalina
- Identify the device type (iPhone, iPad, Mac, Apple Watch, or Apple TV)
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 14.5 or later
- For Mac running macOS 10.15 (Catalina): Go to System Preferences > Software Update and install Security Update 2021-002
- For Mac running macOS 11.x (Big Sur): Go to System Preferences > Software Update and install macOS 11.3 or later
- For Apple Watch: On the iPhone Watch app, go to General > Software Update and install watchOS 7.4 or later
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 14.5 or later
- After updating, verify the device is running the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1882 — 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-1882 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