CVE-2020-3875
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 validation issue was addressed with improved input sanitization. This issue is fixed in iOS 13.3.1 and iPadOS 13.3.1, macOS Catalina 10.15.3, tvOS 13.3.1, watchOS 6.1.2. 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 validation issue in Apple operating systems allowed an application to read restricted memory due to insufficient input sanitization. This represents an out-of-bounds or uninitialized memory read vulnerability affecting iOS, iPadOS, macOS, tvOS, and watchOS.
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< 13.3.1< 13.3.1< 10.15.3< 13.3.1< 6.1.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 iPhoneOpen Settings > General > About and note the version number shown next to 'Version'Affected if Version is lower than 13.3.1 (e.g., 13.3, 13.2.x, etc.)
-
Check iPadOS version on iPadOpen Settings > General > About and note the version number shown next to 'Version'Affected if Version is lower than 13.3.1 (e.g., 13.3, 13.2.x, etc.)
-
Check macOS version on MacClick Apple menu > About This Mac, or run 'sw_vers' in TerminalAffected if Version is lower than 10.15.3 (e.g., 10.15.2, 10.15.1, etc.)
-
Check tvOS version on Apple TVGo to Settings > General > About and note the version numberAffected if Version is lower than 13.3.1 (e.g., 13.3, 13.2.x, etc.)
-
Check watchOS version on Apple WatchOn the paired iPhone, open Watch app > My Watch > General > About, or on the watch go to Settings > General > AboutAffected if Version is lower than 6.1.2 (e.g., 6.1.1, 6.1, etc.)
If any Apple device runs an OS version below 13.3.1 for iOS/iPadOS/tvOS, below 10.15.3 for macOS, or below 6.1.2 for watchOS, the environment is affected by this out-of-bounds memory read 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.
From vendor data6.1.210.15.313.3.1
Apply the vendor-supplied patches by updating to iOS 13.3.1/iPadOS 13.3.1, macOS Catalina 10.15.3, tvOS 13.3.1, or watchOS 6.1.2 or later.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3875 — 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-2020-3875 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