CVE-2021-30962
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 initialization issue was addressed with improved memory handling. This issue is fixed in tvOS 15.2, macOS Big Sur 11.6.2. Parsing a maliciously crafted audio file may lead to disclosure of user information.
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 · moderate confidenceA memory initialization vulnerability in Apple's audio parsing subsystem (likely Core Audio/AudioToolbox) allows processing of a maliciously crafted audio file to disclose sensitive user information from memory due to improper memory handling during parsing.
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>= 11.6, < 11.6.2< 15.2CVSS 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 -productVersion' in Terminal, or go to Apple menu > About This Mac > System Report > Software > System VersionAffected if The version is 11.6, 11.6.1, or 11.6 (Build versions between 20G95 and 21A559)
-
Check tvOS version on Apple TV devicesOn the Apple TV, go to Settings > General > About > Version, or check via Apple Configurator or device management toolsAffected if The version is any release prior to 15.2 (for example 15.0, 15.1, or 15.1.1)
-
Confirm Core Audio / AudioToolbox component is presentOn macOS, verify '/System/Library/Frameworks/AudioToolbox.framework' exists. On tvOS, the AudioToolbox framework is bundled with the system and cannot be individually inspected.Affected if The framework exists (which it does by default on all affected macOS and tvOS installations)
-
Verify the specific Security Update that patches this vulnerability is installedOn macOS, open System Preferences > Security & Privacy > General and look for 'Security Update 2021-006' or later. Alternatively, run 'defaults read /Library/Preferences/com.apple.SoftwareUpdate.plist LastSuccessfulDate' to check the last update time.Affected if No security update is shown or the last update was applied before the November 2021 security patches
Your system is affected if it runs macOS 11.6 or 11.6.1 without Security Update 2021-006, or runs any tvOS version prior to 15.2, and the AudioToolbox framework (present by default) processes a maliciously crafted audio file.
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.215.2
Apply the vendor patches: update to tvOS 15.2 or later, and macOS Big Sur 11.6.2 or later. Until patches are applied, avoid opening audio files from untrusted sources.
macOS Big Sur 11.6.2 or tvOS 15.2
- Check current macOS version: Go to Apple menu > About This Mac
- Check current tvOS version: Go to Settings > General > About > Version
- For macOS: Open System Preferences > Software Update and install the available update to reach version 11.6.2
- For tvOS: Go to Settings > General > Software Update and install the available update to reach version 15.2
- Alternatively, manually download the macOS Big Sur 11.6.2 update from Apple's support downloads page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30962 — 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-30962 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