CVE-2021-30708
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 macOS Big Sur 11.4, Security Update 2021-003 Catalina, Security Update 2021-004 Mojave, iOS 14.6 and iPadOS 14.6. Processing a maliciously crafted USD file may lead to 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 confidenceAn out-of-bounds read vulnerability exists in Apple's handling of USD (Universal Scene Description) files in macOS and iOS. The vulnerability is triggered when processing a maliciously crafted USD file, which can cause unexpected application termination or potentially lead to arbitrary code execution. Apple addressed this with improved input validation in the specified 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.6< 14.6>= 10.14, <= 10.14.5>= 10.15, <= 10.15.6= 10.14.6= 10.15.7>= 11.0, < 11.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 macOS version on the systemRun 'sw_vers -productVersion' in Terminal or check System Preferences > About to obtain the macOS version numberAffected if The version is 10.14.x (through 10.14.5), 10.15.x (through 10.15.6), or 11.0-11.3 (versions below 10.14.6, 10.15.7, or 11.4)
-
Check iOS or iPadOS version on the deviceGo to Settings > General > About on the iOS/iPadOS device to view the versionAffected if The version is any release earlier than 14.6 (including 14.0 through 14.5)
-
Identify if USD file processing capability existsSearch for applications that handle .usd or .usdz files (such as Preview, Quick Look, or 3D rendering tools) using Spotlight or checking the /Applications folderAffected if Any native macOS/iOS application capable of opening USD or USDZ files is present on the system (this is a built-in feature in affected macOS and iOS versions)
-
Verify Quick Look USDZ preview availability (macOS)Create a test .usdz file or locate one, then press Space in Finder to invoke Quick Look and attempt to preview itAffected if Quick Look successfully renders the USDZ file, confirming the vulnerable handler is present and active
The environment is affected if the device runs macOS 10.14.5 or earlier, 10.15.6 or earlier, 11.0-11.3, or any iOS/iPadOS version below 14.6, AND the system has the native capability to process USD/USDZ files which is present by default in these affected OS versions.
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 · scoped11.414.6
Apply the available Apple security updates (macOS Big Sur 11.4 or later, Security Update 2021-003/2021-004 for older macOS, iOS/iPadOS 14.6 or later) to all affected systems.
iOS/iPadOS 14.6; macOS Big Sur 11.4; macOS Catalina Security Update 2021-003; macOS Mojave Security Update 2021-004
- For iOS devices: Go to Settings > General > Software Update and upgrade to iOS 14.6
- For iPadOS devices: Go to Settings > General > Software Update and upgrade to iPadOS 14.6
- For macOS Big Sur (11.x) users: Go to System Preferences > Software Update and upgrade to macOS 11.4
- For macOS Catalina (10.15) users: Go to System Preferences > Software Update and install Security Update 2021-003 Catalina
- For macOS Mojave (10.14) users: Go to System Preferences > Software Update and install Security Update 2021-004 Mojave
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30708 — 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-30708 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