CVE-2021-1809
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. A malicious 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 confidenceThis is a memory corruption vulnerability in Apple's core operating systems (macOS, iOS, iPadOS, watchOS, tvOS) where inadequate memory validation allows a malicious local application to read restricted memory regions. The issue is patched in the mentioned security updates.
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 macOS version on Mac computersRun 'sw_vers -productVersion' in Terminal or view System Preferences > AboutAffected if Version is 10.14.x up to 10.14.6, 10.15.x up to 10.15.7, or 11.0 to 11.2.x (below 11.3)
-
Check iOS version on iPhonesGo to Settings > General > About and note the version number, or run 'idevicesyslog' with device connectedAffected if Version is below 14.5 (for example 14.4.x, 14.3, etc.)
-
Check iPadOS version on iPadsGo to Settings > General > About and note the version numberAffected if Version is below 14.5
-
Check tvOS version on Apple TVGo to Settings > General > About > VersionAffected if Version is below 14.5
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone, go to My Watch > General > AboutAffected if Version is below 7.4
If any Apple device runs an OS version lower than 14.5 (iOS/iPadOS/tvOS/watchOS) or lower than 11.3 (macOS Big Sur) or falls into the specific macOS X 10.14.x/10.15.x ranges listed, it is affected by this 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.411.314.5
Apply the relevant security updates (iOS 14.5, iPadOS 14.5, macOS Big Sur 11.3, Security Update 2021-002/2021-003, watchOS 7.4, tvOS 14.5) to all affected devices and systems.
iOS/iPadOS 14.5+, watchOS 7.4+, tvOS 14.5+, macOS Big Sur 11.3+, Security Update 2021-002 Catalina, Security Update 2021-003 Mojave
- Identify the device type (iPhone, iPad, Mac, Apple Watch, Apple TV)
- Determine the current installed OS version from Settings > General > About (iOS/iPadOS) or System Preferences > Software Update (macOS)
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 14.5 or later
- For Mac: Open System Preferences > Software Update and install the appropriate security update (Security Update 2021-002 for Catalina, Security Update 2021-003 for Mojave, or macOS Big Sur 11.3 or later)
- For Apple Watch: Open the Watch app on iPhone > 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 fix by checking that the OS version matches or exceeds the fixed release for your device
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1809 — 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-1809 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