CVE-2021-30674
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 · uneditedThis issue was addressed with improved checks. This issue is fixed in iOS 14.6 and iPadOS 14.6. A malicious application may disclose restricted memory.
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 disclosure vulnerability in iOS and iPadOS 14.6 and earlier allows a malicious application to read restricted memory contents through an unspecified attack vector. The vulnerability was addressed with improved checks in the iOS 14.6 update.
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.6CVSS 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 iOS version on deviceOn the iOS device, go to Settings > General > About and note the version number displayed next to 'Version'. Alternatively, connect the device to a computer with iTunes or Finder and view the device summary page, or query through MDM if deployed.Affected if The version displayed is less than 14.6 (for example, 14.5, 14.4, 13.x, etc.)
-
Check iPadOS version on deviceOn the iPad device, go to Settings > General > About and note the version number displayed next to 'Version'. For MDM-managed devices, query the OS version through your MDM console.Affected if The version displayed is less than 14.6 (for example, 14.5, 14.4, 13.x, etc.)
-
Verify build number if neededIn Settings > General > About, note the 'Build Number' if the version shows 14.6 but you want to confirm it includes the patch. Compare against known build numbers for iOS 14.6 for your specific model.Affected if The device is running a build of iOS/iPadOS prior to the 14.6 release build.
The device is affected if it is running any version of iOS or iPadOS older than 14.6, as the memory disclosure vulnerability was addressed in that release.
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 · scoped14.6
Update affected iOS/iPadOS devices to version 14.6 or later to patch the memory disclosure vulnerability. In enterprise environments, inventory vulnerable devices and deploy the OS update through mobile device management (MDM) infrastructure.
iOS 14.6 and iPadOS 14.6
- Open the Settings app on your iPhone or iPad
- Tap on 'General'
- Tap on 'Software Update'
- If an update is available, tap 'Download and Install'
- Ensure your device is connected to Wi-Fi and plugged into power during the download and installation
- Wait for the update to download, then follow any on-screen prompts to install it
- After installation, verify your device is running iOS/iPadOS 14.6 or later by going to Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30674 — 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-30674 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