CVE-2021-30725
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 · uneditedA memory corruption issue was addressed with improved state management. 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 confidenceMemory corruption vulnerability in Apple's Universal Scene Description (USD) file parser. Processing a maliciously crafted USD file triggers improper state management leading to memory corruption, which can cause application crashes (denial of service) or potentially allow arbitrary code execution with the privileges of the application parsing the file.
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.5>= 10.15, <= 10.15.6= 10.14.6= 10.15.7>= 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
- 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 view System Preferences > About. On macOS 11.x, note the specific build version.Affected if Version is 10.14.0-10.14.5, 10.14.6, 10.15.0-10.15.6, 10.15.7, or 11.0.1-11.3.x (anything below 11.4 on Big Sur or below 10.14.6/10.15.7 on older macOS)
-
Check iOS/iPadOS versionOn the device, go to Settings > General > About to view the version number.Affected if Version is any release prior to 14.6 (iOS or iPadOS)
-
Identify applications that process USD filesSearch for apps that open .usd, .usda, .usdc, or .usdz files. Use 'mdfind kMDItemContentTypeTree=="com.pixar.universal-scene-description"' or check Application folder for 3D/AR apps like Xcode, Reality Composer, or AR Quick Look-enabled apps.Affected if Any application capable of parsing USD files is installed and available for use on the device
-
Verify USD file processing capability is enabledCheck if AR Quick Look (iOS/iPadOS) or Preview/Quick Look (macOS) can open .usdz files. On iOS, test by opening a USDZ attachment in Mail or Safari.Affected if USD file preview or rendering features are accessible to the user
The environment is affected if the operating system version falls within the ranges specified AND any application or system feature capable of parsing USD files is present and enabled.
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 Apple's security updates (macOS Big Sur 11.4+, Security Update 2021-003/2021-004, iOS/iPadOS 14.6+). In enterprise environments, test USD file processing functionality after applying patches. Restrict processing of USD files from untrusted sources until patches are applied.
iOS 14.6 / iPadOS 14.6 / macOS Big Sur 11.4 / Security Update 2021-003 (Catalina) / Security Update 2021-004 (Mojave)
- Back up all important data before starting the update process
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 14.6 or later
- For macOS Big Sur (11.x): Go to System Preferences > Software Update and install macOS Big Sur 11.4 or later
- For macOS Catalina (10.15.x): Go to System Preferences > Software Update and install Security Update 2021-003 Catalina
- For macOS Mojave (10.14.x): Go to System Preferences > Software Update and install Security Update 2021-004 Mojave
- Restart the device after the update completes
- Verify the update was successful by checking the OS version in Settings/About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30725 — 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-30725 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