CVE-2021-30667
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 iOS 14.6 and iPadOS 14.6. An attacker in WiFi range may be able to force a client to use a less secure authentication mechanism.
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 logic validation flaw in iOS/iPadOS WiFi stack allows an attacker within WiFi range to force a client device to downgrade to a less secure authentication mechanism (e.g., WPA2 instead of WPA3, or weaker EAP methods), potentially enabling credential capture or man-in-the-middle attacks.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/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/iPadOS versionGo to Settings > General > About on the iOS/iPadOS device and note the version number displayed next to 'Version'Affected if The version is lower than 14.6 (e.g., 14.5, 14.4, 13.x, etc.)
-
Confirm WiFi is enabledGo to Settings > WiFi and verify the WiFi toggle is turned onAffected if WiFi is enabled - the device is potentially vulnerable when connected to networks
-
Identify connected network security typeIn Settings > WiFi, tap the connected network (identified by the checkmark) and examine the security type shown (e.g., WPA3, WPA2, WEP, None/Open)Affected if The network uses WPA2 or weaker security, or is an open network with no password
-
Review previously trusted networksIn Settings > WiFi, review the list of 'Known Networks' or remembered networks to identify any that use open or WPA2 authenticationAffected if The device has previously connected to open or WPA2 networks, indicating potential exposure to downgrade attacks
A device is affected if it runs iOS/iPadOS version lower than 14.6 and has WiFi enabled, as the vulnerability can be exploited when the device attempts to connect to or reconnects to WiFi networks.
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
Apply iOS/iPadOS 14.6 or later to affected devices. Avoid connecting to untrusted or open WiFi networks until patched, and prefer WPA3-capable networks where available.
iOS 14.6 / iPadOS 14.6 or later
- Back up your iPhone or iPad device before updating
- Go to Settings > General > Software Update on the device
- Check that iOS 14.6 or iPadOS 14.6 (or a later version) is available
- Download and install the update
- After installation, verify the version by going to Settings > General > About
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-30667 — 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-30667 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