CVE-2023-38572
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 checks. This issue is fixed in iOS 15.7.8 and iPadOS 15.7.8, iOS 16.6 and iPadOS 16.6, tvOS 16.6, macOS Ventura 13.5, Safari 16.6, watchOS 9.6. A website may be able to bypass Same Origin Policy.
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 vulnerability allows a malicious website to bypass the Same Origin Policy (SOP), a fundamental browser security mechanism that isolates web content from different origins. By bypassing SOP, an attacker could potentially read sensitive data, access authentication tokens, or perform actions on behalf of a user from a different origin, leading to cross-site information disclosure or session hijacking.
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< 16.6< 15.7.8>= 16.0, < 16.6< 15.7.8>= 16.0, < 16.6>= 13.0, < 13.5< 16.6< 9.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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, go to Safari menu > About Safari, note the version numberAffected if Version is earlier than 16.6 (e.g., 16.5.x or below)
-
Check iOS version on iPhoneGo to Settings > General > About, note the iOS version numberAffected if iOS version is earlier than 15.7.8, OR between 16.0 and 16.5.x (inclusive)
-
Check iPadOS version on iPadGo to Settings > General > About, note the iPadOS version numberAffected if iPadOS version is earlier than 15.7.8, OR between 16.0 and 16.5.x (inclusive)
-
Check macOS version on MacGo to Apple menu > About This Mac, note the macOS version (Ventura 13.x)Affected if macOS Ventura is earlier than 13.5 (e.g., 13.0 to 13.4)
-
Check tvOS version on Apple TVGo to Settings > General > About TV, note the tvOS version numberAffected if tvOS version is earlier than 16.6
-
Check watchOS version on Apple WatchOpen Watch app on iPhone, go to My Watch > General > About, note the watchOS versionAffected if watchOS version is earlier than 9.6
If any browser or operating system listed above is at a version lower than the patched versions (Safari 16.6, iOS/iPadOS 15.7.8 or 16.6, macOS 13.5, tvOS 16.6, watchOS 9.6), the Same Origin Policy bypass vulnerability is present.
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.613.515.7.8
Apply the vendor-supplied security updates: iOS 15.7.8/16.6, iPadOS 15.7.8/16.6, tvOS 16.6, macOS Ventura 13.5, Safari 16.6, or watchOS 9.6 depending on the affected device.
iOS 15.7.8 / iOS 16.6 / iPadOS 15.7.8 / iPadOS 16.6 / tvOS 16.6 / macOS Ventura 13.5 / Safari 16.6 / watchOS 9.6
- Identify the current operating system version on the affected Apple device (iPhone, iPad, Mac, Apple TV, or Apple Watch)
- For iOS/iPadOS devices: If running iOS/iPadOS 15.x, upgrade to version 15.7.8; if running iOS/iPadOS 16.x, upgrade to version 16.6
- For macOS devices: If running macOS Ventura 13.x, upgrade to version 13.5
- For tvOS devices: Upgrade to version 16.6
- For watchOS devices: Upgrade to version 9.6
- For Safari on older macOS: Upgrade Safari to version 16.6
- Back up the device before applying the update (recommended)
- Install the update via Settings > General > Software Update on iOS/iPadOS, or System Settings > Software Update on macOS, or via the Settings app on Apple TV/Watch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38572 — 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-2023-38572 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