CVE-2021-1875
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 double free issue was addressed with improved memory management. 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. Processing a maliciously crafted file may lead to heap corruption.
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 double-free memory corruption vulnerability in Apple products (iOS, iPadOS, watchOS, tvOS, macOS) allows heap corruption when processing a maliciously crafted file. The vulnerability stems from improper memory management during file parsing, potentially enabling arbitrary code execution.
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.0= 10.14.1= 10.14.2= 10.14.3= 10.14.4= 10.14.5= 10.14.6= 10.15= 10.15.1= 10.15.2= 10.15.3>= 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
- 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 iPhoneGo to Settings > General > About > Version and note the displayed version number (e.g., 14.4.1)Affected if The version is less than 14.5 (e.g., 14.4, 14.3, etc.)
-
Check iPadOS version on iPadGo to Settings > General > About > Version and note the displayed version numberAffected if The version is less than 14.5
-
Check macOS version on MacClick the Apple menu > About This Mac and note the version number (e.g., 11.2.3, 10.15.7)Affected if The version is 10.14.x, 10.15.x, or between 11.0 and 11.2.x (anything less than 11.3)
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone, go to My Watch > General > About and note the watchOS versionAffected if The version is less than 7.4
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on Apple TV and note the version numberAffected if The version is less than 14.5
If any Apple device (iPhone, iPad, Mac, Apple Watch, or Apple TV) runs a version lower than the patched release (iOS/iPadOS/tvOS < 14.5, watchOS < 7.4, or macOS < 11.3 for Big Sur / specific 10.14/10.15 versions), the device is vulnerable.
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 vendor-supplied security updates (iOS 14.5, iPadOS 14.5, watchOS 7.4, tvOS 14.5, macOS Big Sur 11.3, Security Update 2021-002/2021-003) to all affected devices and systems.
iOS 14.5+, iPadOS 14.5+, watchOS 7.4+, tvOS 14.5+, macOS Big Sur 11.3+, Security Update 2021-002 (Catalina), Security Update 2021-003 (Mojave)
- For iPhone: Go to Settings > General > Software Update and install iOS 14.5 or later
- For iPad: Go to Settings > General > Software Update and install iPadOS 14.5 or later
- For Apple Watch: Open the Watch app on iPhone, go to My Watch > 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
- For macOS Big Sur (11.0-11.2): Go to System Preferences > Software Update and install macOS 11.3 or later
- For macOS Catalina (10.14.x): Install Security Update 2021-002 from Apple Support downloads
- For macOS Mojave (10.14.x): Install Security Update 2021-003 from Apple Support downloads
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-1875 — 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-1875 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