CVE-2020-29610
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 read was addressed with improved input validation. This issue is fixed in watchOS 7.2, macOS Big Sur 11.1, Security Update 2020-001 Catalina, Security Update 2020-007 Mojave, iOS 14.3 and iPadOS 14.3, tvOS 14.3. Processing a maliciously crafted audio file may disclose 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 confidenceOut-of-bounds read vulnerability in Apple's media processing stack that allows disclosure of restricted memory when processing a maliciously crafted audio file. The fix implemented improved input validation to prevent reading beyond allocated buffer boundaries.
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.3< 14.3>= 10.14, < 10.14.6>= 10.15, < 10.15.7= 10.14.6= 10.15.7>= 11.0, < 11.1.0< 14.3< 7.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.
-
Identify your Apple device and operating systemDetermine whether the device is an iPhone, iPad, Mac, Apple Watch, or Apple TV. On iOS/iPadOS, go to Settings > General > About. On macOS, click Apple menu > About This Mac. On watchOS, go to Settings > General > About. On tvOS, go to Settings > General > About.Affected if The device runs iOS, iPadOS, macOS, watchOS, or tvOS.
-
Check iOS or iPadOS versionOn iPhone or iPad, go to Settings > General > About and note the version number (for example, 14.2 or 14.3).Affected if The version is earlier than 14.3 (such as 14.2, 14.1, or 14.0).
-
Check macOS versionOn Mac, click the Apple menu > About This Mac and note the version number (for example, 10.15.7, 11.0.1, or 11.1).Affected if The version is 10.14.x before 10.14.6, 10.15.x before 10.15.7, or 11.0.x before 11.1.0.
-
Check watchOS or tvOS versionOn Apple Watch, go to Settings > General > About and note the version. On Apple TV, go to Settings > General > About and note the version.Affected if The watchOS version is earlier than 7.2 or the tvOS version is earlier than 14.3.
You are affected if your device runs iOS/iPadOS earlier than 14.3, macOS 10.14.x before 10.14.6 or 10.15.x before 10.15.7, macOS 11.0.x before 11.1.0, watchOS earlier than 7.2, or tvOS earlier than 14.3.
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.210.14.610.15.7
Apply the appropriate Apple security update for the affected product: iOS 14.3/iPadOS 14.3, macOS Big Sur 11.1/Catalina Security Update 2020-001/Mojave Security Update 2020-007, watchOS 7.2, or tvOS 14.3.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-29610 — 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-29610 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