CVE-2021-1808
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, Security Update 2021-003 Mojave, iOS 14.5 and iPadOS 14.5, watchOS 7.4, tvOS 14.5, macOS Big Sur 11.3. An application may be able to read restricted memory.
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 corruption vulnerability in Apple operating systems allowed applications to read restricted memory due to insufficient validation. The flaw was addressed through improved memory validation checks in the affected system components.
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.14, <= 10.14.5>= 10.15, <= 10.15.5= 10.14.6= 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 and note the Version numberAffected if Version is less than 14.5 (e.g., 14.4, 14.3, etc.)
-
Check iPadOS version on iPadGo to Settings > General > About and note the Version numberAffected if Version is less than 14.5
-
Check macOS version on MacClick Apple menu > About This Mac to view the version numberAffected if Version is 10.14.x through 10.14.5, 10.15.x through 10.15.6, 10.15.7, or 11.0 through 11.2.x (not 11.3 or later)
-
Check tvOS version on Apple TVGo to Settings > General > About > VersionAffected if Version is less than 14.5
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone, go to My Watch > General > About to see watchOS versionAffected if Version is less than 7.4
Your device is affected if the installed operating system version falls within any of the ranges listed: iOS/iPadOS/tvOS/watchOS below 14.5/7.4, macOS 10.14.x-10.14.5, 10.15.x-10.15.7, or macOS 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 appropriate Apple security update: Security Update 2021-002 for macOS Catalina, Security Update 2021-003 for macOS Mojave, macOS Big Sur 11.3, iOS 14.5/iPadOS 14.5, watchOS 7.4, or tvOS 14.5.
iOS 14.5+/iPadOS 14.5+/watchOS 7.4+/tvOS 14.5+/macOS 11.3+ (or Security Update 2021-002/2021-003 for older macOS)
- Identify the affected device type (iPhone, iPad, Mac, Apple Watch, or Apple TV)
- Determine the current installed OS version from Settings > General > About (iOS/iPadOS) or System Preferences > About (macOS)
- For iPhone/iPad: Upgrade to iOS 14.5 or later / iPadOS 14.5 or later via Settings > General > Software Update
- For Mac: Upgrade to macOS Big Sur 11.3 or later, or apply Security Update 2021-002 (Catalina) or Security Update 2021-003 (Mojave) via System Preferences > Software Update
- For Apple Watch: Upgrade to watchOS 7.4 or later via the Watch app on iPhone > General > Software Update
- For Apple TV: Upgrade to tvOS 14.5 or later via Settings > System > Software Updates
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-1808 — 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-1808 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