CVE-2021-30979
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 buffer overflow issue was addressed with improved memory handling. 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 buffer overflow vulnerability exists in the USD (Universal Scene Description) file parsing components across macOS and iOS. Processing a maliciously crafted USD file with specially crafted data can overflow a memory buffer, leading to memory corruption that enables either denial of service (application crash) or 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< 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' or go to Apple menu > About This Mac to determine the installed macOS versionAffected if Version is 10.15.7, or between 10.15 and 10.15.7, or between 11.0 and 11.6.2, or between 12.0 and 12.1
-
Check iOS/iPadOS versionGo to Settings > General > About on iPhone or iPad to determine the iOS/iPadOS versionAffected if Version is less than 15.2
-
Identify USD parsing applicationsCheck for applications that process USD files such as Final Cut Pro, Motion, Compressor, or third-party USD viewers installed on the systemAffected if Any USD-capable application is installed and the OS version falls within the affected ranges above
-
Verify USD framework presenceRun 'ls /System/Library/Frameworks/ | grep -i usd' or check for presence of USD framework in Application directoriesAffected if USD framework or USD-enabled applications are present on an affected OS version
-
Inspect running processes for USD activityUse Activity Monitor to see if any applications are currently parsing USD files, or check recent file access logs for .usd, .usda, .usdc, .usdz file extensionsAffected if USD files are being processed on a vulnerable system
The system is affected if it runs macOS 10.15.7, 10.15.x, 11.0-11.6.2, or 12.0-12.1, or iOS/iPadOS prior to 15.2, and has USD file parsing capabilities enabled through installed applications or frameworks.
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 · scoped10.15.711.6.212.1
Apply the vendor-supplied security updates: macOS Monterey 12.1, iOS 15.2/iPadOS 15.2, macOS Big Sur 11.6.2, or Security Update 2021-008 for Catalina. Until patched, avoid opening USD files from untrusted or unknown sources.
iOS 15.2 / iPadOS 15.2 / macOS Big Sur 11.6.2 / macOS Monterey 12.1 / Security Update 2021-008 for Catalina (10.15.7)
- Identify the current version of macOS, iOS, or iPadOS on the affected device
- For iPhone and iPad: Go to Settings > General > Software Update and install iOS 15.2 or iPadOS 15.2
- For macOS Big Sur (11.x): Go to System Preferences > Software Update and install macOS Big Sur 11.6.2
- For macOS Monterey (12.x): Go to System Preferences > Software Update and install macOS Monterey 12.1
- For macOS Catalina (10.15.x): Install Security Update 2021-008 (or update to macOS 10.15.7 if not already on that version)
- After updating, verify the installation was successful by checking the installed version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30979 — 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-30979 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