CVE-2021-30746
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 disclose memory contents.
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 vulnerability in Apple's USD (Universal Scene Description) file processing component allows an out-of-bounds read when parsing a maliciously crafted USD file. The flaw stems from insufficient input validation, enabling an attacker to read adjacent memory contents beyond allocated buffers.
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.0= 10.14.1= 10.14.2= 10.14.3= 10.14.4= 10.14.5= 10.14.6= 10.15= 10.15.1= 10.15.2= 10.15.3= 10.15.4>= 11.0.1, < 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
- 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 macOS version on the systemRun 'sw_vers' in Terminal or go to Apple menu > About This Mac to view the macOS version numberAffected if The version shown is 10.14.0 through 10.15.4, or 11.0.1 through 11.3.x (anything below 11.4)
-
Check iOS or iPadOS version on iPhone or iPadGo to Settings > General > About on the iOS device and note the version numberAffected if The version shown is anything below 14.6 (for example, 14.5, 14.4, etc.)
-
Identify if USD file processing is in useCheck if any applications on the system open or handle .usd, .usda, .usdc, or .usdz files. Common apps include Finder Quick Look, Xcode, or third-party 3D toolsAffected if The system can open or preview USD files and the OS version is in the affected range listed above
-
Verify Quick Look preview capability (macOS)Select any .usd/.usdz file in Finder and press Space to trigger Quick Look previewAffected if Quick Look successfully renders the file and the macOS version is vulnerable
-
Check for Security Update installations (macOS)Run 'system_profiler SPSoftwareDataType' in Terminal and look at the macOS build version, or check System Preferences > Software Update for installed updatesAffected if The system shows no security updates installed after the fix dates and the base OS version remains vulnerable
A user is affected if their device runs iOS/iPadOS below 14.6 or macOS between 10.14.0-10.15.4 or 11.0.1-11.3.x, and they open or preview maliciously crafted USD files.
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 relevant Apple security updates (macOS Big Sur 11.4, Security Update 2021-003/2021-004, iOS/iPadOS 14.6) to all affected devices. Avoid opening untrusted USD files from unknown sources.
iOS 14.6, iPadOS 14.6, macOS Big Sur 11.4, Security Update 2021-003 Catalina, Security Update 2021-004 Mojave
- For iOS/iPadOS devices: Go to Settings > General > Software Update and install iOS/iPadOS 14.6
- For macOS Big Sur (11.x): Go to System Preferences > Software Update and install macOS Big Sur 11.4
- For macOS Catalina (10.15): Go to System Preferences > Software Update and install Security Update 2021-003 Catalina
- For macOS Mojave (10.14): 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.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30746 — 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-30746 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