CVE-2020-9876
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 · uneditedAn out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 13.6 and iPadOS 13.6, macOS Catalina 10.15.6, tvOS 13.4.8, watchOS 6.2.8, iTunes 12.10.8 for Windows, iCloud for Windows 11.3, iCloud for Windows 7.20. Opening a maliciously crafted PDF file may lead to an unexpected application termination or arbitrary code execution.
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 an out-of-bounds write vulnerability in Apple's core frameworks (likely CoreGraphics or PDFKit) affecting iOS, iPadOS, macOS, tvOS, watchOS, iTunes, and iCloud for Windows. The vulnerability is triggered when a user opens a maliciously crafted PDF file, causing memory corruption that can lead to arbitrary code execution. The issue was addressed with improved bounds checking in the respective 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< 7.20>= 10.0, < 11.5< 12.10.9< 14.0< 14.0>= 10.13, < 10.13.6>= 10.14, < 10.14.6>= 10.15, < 10.15.6= 10.13.6= 10.14.6>= 11.0, <= 11.0.1< 14.0< 7.0CVSS 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.
-
Identify the Apple product in useDetermine whether the system is running iOS, iPadOS, macOS, tvOS, watchOS, iTunes, or iCloud for Windows. On macOS, check System Preferences > About. On iOS/iPadOS, check Settings > General > About. For iTunes/iCloud, check the application version in the app itself or the Windows Programs and Features list.Affected if The product is one of the affected: iCloud, iTunes, iPadOS, iPhone OS, macOS, tvOS, or watchOS.
-
Determine the installed version numberOn macOS, run 'sw_vers' in Terminal or check System Preferences > About. On iOS/iPadOS, go to Settings > General > About and note the version number. On tvOS/watchOS, check in Settings > General > About. For iTunes on Windows, open iTunes > Help > About iTunes. For iCloud for Windows, open the app and check the version in settings.Affected if Version number cannot be determined or does not match the expected format for comparison.
-
Compare against affected macOS versionsFor macOS: versions 10.13.x before 10.13.6, 10.14.x before 10.14.6, 10.15.x before 10.15.6, and versions 11.0 to 11.0.1 are affected. Run 'sw_vers -productVersion' to get the exact version.Affected if The installed macOS version falls within: 10.13.0-10.13.5, 10.14.0-10.14.5, 10.15.0-10.15.5, or 11.0-11.0.1.
-
Compare against affected iOS/iPadOS versionsFor iOS and iPadOS, check the version in Settings > General > About. Versions prior to 14.0 are affected (including all 13.x versions before 13.6).Affected if The installed iOS or iPadOS version is below 14.0.
-
Compare against affected tvOS/watchOS versionsFor tvOS, versions before 14.0 are affected. For watchOS, versions before 7.0 are affected. Check via Settings > General > About on each device.Affected if The tvOS version is below 14.0 or the watchOS version is below 7.0.
-
Compare against affected iTunes and iCloud versionsFor iTunes (Windows or macOS), check Help > About iTunes - versions before 12.10.9 are affected. For iCloud for Windows, check the version in the app settings - versions before 7.20 or in the range >=10.0 to <11.5 are affected.Affected if iTunes is below 12.10.9, or iCloud for Windows is below 7.20 or between 10.0 and 11.4.
The system is affected if the installed product and version matches any of the affected ranges AND the system has the ability to open or process PDF files (which is default in all listed products).
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 data7.07.2010.13.6
Apply the vendor security updates (iOS 13.6+, iPadOS 13.6+, macOS 10.15.6+, tvOS 13.4.8+, watchOS 6.2.8+, iTunes 12.10.8+, iCloud for Windows 11.3+/7.20+) and avoid opening PDF files from untrusted or unknown sources.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9876 — 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-9876 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