CVE-2021-30971
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 macOS Monterey 12.1, iOS 15.2 and iPadOS 15.2, macOS Big Sur 11.6.2, Security Update 2021-008 Catalina. 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 confidenceA memory corruption vulnerability exists in Apple's USD (Universal Scene Description) file parser. The vulnerability is an out-of-bounds write issue caused by insufficient bounds checking when processing USD files. A specially crafted malicious USD file can trigger the vulnerability during parsing, leading to application termination or arbitrary code execution with the privileges of the vulnerable application.
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< 15.2< 15.2>= 10.15, <= 10.15.7= 10.15.7>= 11.0, < 11.6.2>= 12.0, < 12.1CVSS 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 versionRun 'sw_vers' in Terminal or System Preferences > About to find the exact macOS version numberAffected if Version is 10.15.x, 11.0-11.6.1, or 12.0-12.0 (before 12.1)
-
Check iOS/iPadOS versionGo to Settings > General > About on iPhone or iPad to view the versionAffected if Version is before 15.2 (e.g., 15.0, 15.1, or earlier)
-
Identify USD-handling applicationsSearch for applications that open .usd, .usda, .usdc, or .usdz files: use 'mdfind kMDItemContentTypeTree == "com.pixar.universal-scene-description"' or check commonly used apps like Preview, QuickLook, or 3D modeling toolsAffected if Any application that parses USD files is present on the system
-
Check for applied security updatesRun 'system_profiler SPSoftwareDataType' and look for Security Updates in the output, or check for specific update 2021-008 for macOS CatalinaAffected if No security updates dated after December 2021 are installed on vulnerable macOS versions
A user is affected if their device runs macOS 10.15.x, 11.0-11.6.1, or 12.0, or iOS/iPadOS before 15.2, and they open or preview untrusted USD/USDZ files using built-in Apple applications.
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.6.212.115.2
Apply the vendor-supplied security updates: macOS Monterey 12.1 or later, iOS/iPadOS 15.2 or later, macOS Big Sur 11.6.2, or Security Update 2021-008 for Catalina. Alternatively, avoid opening untrusted USD files from unknown sources.
iOS 15.2+, iPadOS 15.2+, macOS Monterey 12.1+, macOS Big Sur 11.6.2+, or Security Update 2021-008 for macOS Catalina
- Identify the device type: iPhone, iPad, or Mac
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 15.2/iPadOS 15.2 or later
- For Mac: Open System Preferences > Software Update and install the latest security update (macOS Monterey 12.1, Big Sur 11.6.2, or Security Update 2021-008 for Catalina)
- Restart the device after applying the update
- Verify the update was successfully installed by checking Settings > General > About (iOS/iPadOS) or System Preferences > Software Update (macOS)
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2021-30971 — 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-30971 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