CVE-2022-32855
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 state management. This issue is fixed in iOS 15.6 and iPadOS 15.6. A user may be able to view restricted content from the lock screen.
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 error in iOS and iPadOS versions prior to 15.6 allowed improper state management that could expose restricted content (such as notifications, messages, or other sensitive data) directly from the lock screen, bypassing intended access controls.
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.6< 15.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
- 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 installed iOS versionGo to Settings > General > About on the iOS device and locate the 'Version' field. Alternatively, connect the device to a computer with iTunes or Finder and view the device summary page which displays the iOS version.Affected if The version number is lower than 15.6 (for example, 15.5, 15.4, 15.3, etc.)
-
Check installed iPadOS versionGo to Settings > General > About on the iPadOS device and locate the 'Version' field. Alternatively, connect the device to a computer with iTunes or Finder and view the device summary page which displays the iPadOS version.Affected if The version number is lower than 15.6 (for example, 15.5, 15.4, 15.3, etc.)
-
Verify lock screen notification settingsGo to Settings > Notifications > Show Previews on the device. Examine whether 'When Unlocked', 'Always', or similar options are selected that allow sensitive content to appear on the lock screen.Affected if The device is running iOS/iPadOS version below 15.6 AND the lock screen is configured to display message previews, notification content, or other sensitive data visible without authentication.
The device is affected if it runs iOS or iPadOS version 15.5 or earlier and has lock screen settings configured to display sensitive content such as message previews or notification details.
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.6
Update affected iOS/iPadOS devices to version 15.6 or later to obtain the corrected logic for state management that properly enforces lock screen content restrictions.
iOS 15.6 or iPadOS 15.6
- Back up your iPhone or iPad to iCloud or your computer before updating
- Connect your device to power and ensure it is connected to Wi-Fi
- Open the Settings app on your device
- Tap on 'General'
- Tap on 'Software Update'
- Download and install iOS 15.6 (for iPhone) or iPadOS 15.6 (for iPad) when it appears
- Follow any on-screen instructions to complete the installation
- After the device restarts, verify the update by going to Settings > General > About to confirm the 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-2022-32855 — 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-32855 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