CVE-2022-22642
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 15.4 and iPadOS 15.4. A user may be able to bypass the Emergency SOS passcode prompt.
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 confidenceThis is an iOS/iPadOS vulnerability (CVE-2022-22642) that allows a user to bypass the Emergency SOS passcode prompt. The Emergency SOS feature normally requires a passcode entry after emergency calls to prevent unauthorized device use. The vulnerability was addressed with improved checks and fixed in iOS 15.4 and iPadOS 15.4.
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.4< 15.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 versionOpen Settings > General > About on the iPhone or iPad and note the version number displayed next to "Version"Affected if The version is earlier than 15.4 (for example, 15.3.2, 15.3.1, 15.3, 15.2, etc.)
-
Check iPadOS versionOpen Settings > General > About on the iPad and note the version number displayed next to "Version"Affected if The version is earlier than 15.4 (for example, 15.3.2, 15.3.1, 15.3, 15.2, etc.)
-
Verify Emergency SOS capabilityConfirm the device is an iPhone or iPad model that supports Emergency SOS. This feature is available on all iPhones and cellular-capable iPadsAffected if The device is an iPhone or cellular iPad running iOS/iPadOS below version 15.4
A device is affected if it is an iPhone or iPad running iOS or iPadOS version lower than 15.4, as the vulnerability allows bypassing the Emergency SOS passcode prompt.
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.4
Update affected iOS/iPadOS devices to version 15.4 or later to remediate this vulnerability. This can be done via MDM (Mobile Device Management) or direct device update.
iOS 15.4 and iPadOS 15.4
- Backup your iPhone or iPad to iCloud or your computer before updating
- Ensure your device is connected to Wi-Fi and plugged into power
- Go to Settings > General > Software Update on your device
- Tap 'Download and Install' when iOS 15.4 or iPadOS 15.4 is available
- Enter your passcode if prompted and confirm the update
- Wait for the update to download and install - your device will restart
- After updating, verify the version by going to Settings > General > About and confirm it shows iOS/iPadOS 15.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22642 — 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-2022-22642 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