SafariWeb browser · Apple
CVE-2022-42852
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 · uneditedThe issue was addressed with improved memory handling. This issue is fixed in Safari 16.2, tvOS 16.2, macOS Ventura 13.1, iOS 15.7.2 and iPadOS 15.7.2, iOS 16.2 and iPadOS 16.2, watchOS 9.2. Processing maliciously crafted web content may result in the disclosure of process 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 · high confidenceA memory handling vulnerability in WebKit allows processing of maliciously crafted web content to disclose process memory. This is an information disclosure flaw affecting Safari, iOS, iPadOS, macOS, tvOS, and watchOS.
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
SafariWeb browser
< 16.2< 15.7.2>= 16.0, < 16.2< 15.7.2>= 16.0, < 16.2= 13.0< 16.2< 9.2CVSS 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 Safari version on macOS or iOS/iPadOSOn macOS: Open Safari > Safari menu > About Safari. On iOS/iPadOS: Settings > Safari > About. Compare the version number to the affected range (< 16.2).Affected if Safari version is lower than 16.2
-
Check iPadOS versionGo to Settings > General > About. Look for the version number. Compare to affected ranges: < 15.7.2 OR (>= 16.0 AND < 16.2).Affected if iPadOS version is 15.7.1 or earlier, or between 16.0 and 16.1 inclusive
-
Check iPhone iOS versionGo to Settings > General > About. Look for the version number. Compare to affected ranges: < 15.7.2 OR (>= 16.0 AND < 16.2).Affected if iOS version is 15.7.1 or earlier, or between 16.0 and 16.1 inclusive
-
Check macOS versionOpen System Settings > About (or Apple menu > About This Mac). Look for the version number (e.g., 13.0). Compare to affected range: = 13.0 exactly.Affected if macOS version is exactly 13.0 (Ventura)
A user is affected if any WebKit-based application (Safari, browser in iOS/iPadOS, etc.) runs on a version lower than the patched releases: Safari 16.2, iOS/iPadOS 15.7.2 or 16.2, macOS 13.1, tvOS 16.2, or watchOS 9.2.
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.215.7.216.2
Update affected Apple products to the patched versions: Safari 16.2, iOS/iPadOS 15.7.2 or 16.2, macOS Ventura 13.1, tvOS 16.2, or watchOS 9.2.
Safari 16.2, tvOS 16.2, macOS Ventura 13.1, iOS 15.7.2/16.2, iPadOS 15.7.2/16.2, watchOS 9.2
- Upgrade Safari to version 16.2
- Upgrade tvOS to version 16.2
- Upgrade macOS Ventura to version 13.1
- Upgrade iOS to version 15.7.2 (for iOS 15.x devices) or iOS 16.2 (for iOS 16.x devices)
- Upgrade iPadOS to version 15.7.2 (for iPadOS 15.x devices) or iPadOS 16.2 (for iPadOS 16.x devices)
- Upgrade watchOS to version 9.2
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42852 — 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-42852 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