CVE-2021-30882
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 logic issue was addressed with improved validation. This issue is fixed in watchOS 8, iOS 15 and iPadOS 15. An application with microphone permission may unexpectedly access microphone input during a FaceTime call.
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 logic validation flaw in iOS 15, iPadOS 15, and watchOS 8 allows any application with microphone permissions to unexpectedly access the device microphone during an active FaceTime call, potentially enabling unauthorized audio surveillance without explicit user awareness during the call.
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.0< 15.0< 8.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 iOS version on iPhoneGo to Settings > General > About > Version to view the installed iOS versionAffected if Version is earlier than 15.0 (for example, 14.x)
-
Check iPadOS version on iPadGo to Settings > General > About > Version to view the installed iPadOS versionAffected if Version is earlier than 15.0 (for example, 14.x)
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone, go to My Watch > General > About to view watchOS versionAffected if Version is earlier than 8.0 (for example, 7.x)
-
Review microphone permissions granted to appsGo to Settings > Privacy > Microphone to see which third-party apps have microphone accessAffected if Any third-party app is listed with microphone permission granted while using a vulnerable iOS/iPadOS version
The device is affected if it runs iOS or iPadOS versions earlier than 15.0, or watchOS earlier than 8.0, and has third-party apps with microphone permissions that could be exploited during FaceTime calls.
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 · scoped8.015.0
Update affected devices to iOS 15 or later, iPadOS 15 or later, and watchOS 8 or later to receive the improved validation fix.
iOS 15 / iPadOS 15 / watchOS 8.0 (depending on device type)
- Back up your device using iCloud or Finder/iTunes before updating
- On iPhone or iPad: Go to Settings > General > Software Update and install iOS 15 or iPadOS 15
- On Apple Watch: Open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 8.0
- After updating, verify the update by checking Settings > General > About for the correct version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30882 — 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-30882 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