SafariWeb browser · Apple
CVE-2022-32833
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 · uneditedAn issue existed with the file paths used to store website data. The issue was resolved by improving how website data is stored. This issue is fixed in iOS 16. An unauthorized user may be able to access browsing history.
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 confidenceThis is an information disclosure vulnerability in iOS where improper file path handling for website data storage allows unauthorized access to browsing history. The vulnerability stems from insecure file permissions or predictable file paths used to store website data locally on the device, potentially allowing a local attacker to read sensitive browsing information.
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.0< 16.0< 13.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 macOSOpen Safari, click Safari menu > About Safari, note the version number displayedAffected if Version is lower than 16.0 (e.g., 15.x)
-
Check iOS version on iPhone/iPadOpen Settings > General > About, look for the 'Version' entry showing iOS version numberAffected if iOS version is lower than 16.0 (e.g., 15.x)
-
Check macOS versionOpen System Preferences (System Settings on newer macOS) > General > About, note the macOS version numberAffected if macOS version is lower than 13.0 (e.g., 12.x or earlier)
-
Verify if Safari website data is presentIn Safari, go to Safari > Settings > Privacy > Manage Website Data to see stored browsing dataAffected if Website data storage is actively used (list of websites appears); combined with vulnerable version, this indicates potential exposure
You are affected if Safari is below version 16.0, or iOS is below 16.0, or macOS is below 13.0, AND you use Safari with stored website data.
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 · scoped13.016.0
Update affected devices to iOS 16 or later, as Apple resolved this by improving how website data is stored. For organizations, deploy iOS updates through MDM or ensure users update their devices.
Safari 16.0, iOS 16.0, macOS 13.0
- For Safari on macOS: Update macOS to version 13.0 or later, which includes Safari 16.0 or later
- For iOS devices (iPhone/iPad): Update iOS to version 16.0 or later via Settings > General > Software Update
- For macOS computers: Update macOS to version 13.0 or later via System Preferences > Software Update
- After updating, verify Safari version is 16.0 or later via Safari > About Safari
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- 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-32833 — 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-32833 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