CVE-2022-42817
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.7.1 and iPadOS 15.7.1, iOS 16.1 and iPadOS 16, watchOS 9.1. Visiting a maliciously crafted website may leak sensitive data.
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 flaw in iOS, iPadOS, and watchOS allows malicious websites to bypass state management protections and leak sensitive user data. The vulnerability is triggered when a victim visits a crafted webpage, potentially exposing cross-origin data due to improper handling of browser state transitions.
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.7.1< 15.7.1= 16.0< 9.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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 iPhoneGo to Settings > General > About on the iPhone and note the version number. Compare it to the affected range: less than 15.7.1 or exactly 16.0.Affected if The iOS version is less than 15.7.1 or equals 16.0 exactly.
-
Check iPadOS version on iPadGo to Settings > General > About on the iPad and note the version number. Compare it to the affected range: less than 15.7.1.Affected if The iPadOS version is less than 15.7.1.
-
Check watchOS version on Apple WatchOpen the Watch app on the paired iPhone, go to General > About, and check the watchOS version. Compare to affected range: less than 9.1.Affected if The watchOS version is less than 9.1.
-
Verify browser usageDetermine if Safari or any app using WebKit (the Apple web engine) has been used on the device. This includes the default Safari browser and third-party browsers that embed WebKit.Affected if The device OS is in the affected version range AND Safari or WebKit-based apps have been used to visit untrusted websites.
The device is affected if it runs iOS/iPadOS below 15.7.1 (or exactly 16.0) or watchOS below 9.1, and the user has browsed the web using Safari or any WebKit-based application.
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 · scoped9.115.7.1
Update affected devices to iOS 15.7.1/iPadOS 15.7.1, iOS 16.1/iPadOS 16, watchOS 9.1 or later. For enterprise environments, deploy the update via MDM and verify compliance.
iOS 15.7.1 / iPadOS 15.7.1 / iOS 16.1+ / iPadOS 16.1+ / watchOS 9.1+
- Determine your current iOS/iPadOS version by going to Settings > General > About
- If running iOS/iPadOS 15.x versions below 15.7.1, upgrade to iOS 15.7.1 or iPadOS 15.7.1
- If running iOS/iPadOS 16.0, upgrade to iOS 16.1 or later (iPadOS 16.1 or later)
- For Apple Watch, if running watchOS versions below 9.1, upgrade to watchOS 9.1 or later
- To upgrade, go to Settings > General > Software Update on the device, or connect to Finder/iTunes on a computer
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-2022-42817 — 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-42817 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