CVE-2021-30967
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 · uneditedDescription: A permissions issue was addressed with improved validation. This issue is fixed in iOS 15.2 and iPadOS 15.2. A local attacker may be able to read sensitive 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 permissions issue in iOS allowed a local attacker to read sensitive information due to insufficient validation. The vulnerability was addressed through improved validation checks and is fixed in iOS 15.2 and iPadOS 15.2.
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.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 iOS version installedGo to Settings > General > About > Version on the iPhone or iPad, or query via MDM or Apple ConfiguratorAffected if The version number is less than 15.2 (for example, 15.1, 15.0, 14.x, etc.)
-
Check iPadOS version installedGo to Settings > General > About > Version on the iPad, or query via MDM or Apple ConfiguratorAffected if The version number is less than 15.2
-
Identify if device has apps with excessive permissionsReview installed applications in Settings > Privacy and compare against expected enterprise apps; check for any unknown or suspicious third-party appsAffected if Unknown apps with access to Contacts, Photos, or other sensitive data are present on a device running iOS/iPadOS < 15.2
-
Check for signs of unauthorized local accessReview device audit logs if available through MDM, look for unusual unlock patterns or device enrollment changesAffected if Evidence of multiple failed unlock attempts or unexpected device configuration changes on a vulnerable iOS version
The device is affected if it runs iOS or iPadOS version lower than 15.2, as the insufficient validation flaw allowing a local attacker to read sensitive data exists in those versions.
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 · scoped15.2
Update affected iOS devices to version 15.2 or later to remediate this vulnerability.
iOS 15.2 / iPadOS 15.2
- Back up your device data before performing the update
- Connect your device to power and Wi-Fi
- Go to Settings > General > Software Update
- Download and install iOS 15.2 or iPadOS 15.2
- Restart the device after the update completes
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-30967 — 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-30967 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