dbcve.org
SafariWeb browser · Apple

CVE-2023-32402

MEDIUM · 6.5 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to 9.5 / 13.4 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
An out-of-bounds read was addressed with improved input validation. This issue is fixed in watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, Safari 16.5, iOS 16.5 and iPadOS 16.5. Processing web content may disclose sensitive information.

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 confidence

An out-of-bounds read vulnerability in WebKit allows processing of malicious web content to disclose sensitive information. The issue was addressed through improved input validation. The vulnerability affects Safari and web rendering components across watchOS, tvOS, macOS, iOS, and iPadOS.

MitigationApply the available security updates (watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, Safari 16.5, iOS 16.5, iPadOS 16.5 or later) to all affected devices and systems.

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
Affected:< 16.5
IpadosOperating system
Affected:>= 16.0, < 16.5
Iphone OsOperating system
Affected:>= 16.0, < 16.5
macOSOperating system
Affected:>= 13.0, < 13.4
TvosOperating system
Affected:< 16.5
WatchosOperating system
Affected:< 9.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Apple product in use
    Determine whether the system is running macOS, iOS, iPadOS, tvOS, watchOS, or if Safari is the standalone application being checked. On macOS, you can check System Settings > About to see the macOS version. On iOS/iPadOS, go to Settings > General > About. On Apple TV, go to Settings > General > About. On Apple Watch, open the Settings app on the watch and go to General > About.
    Affected if Any of the affected products listed in the CVE is in use
  2. Check the installed macOS version
    On macOS, open System Settings > General > About, or run 'sw_vers' in Terminal. Look for the version number (e.g., 13.3, 13.4, 13.5).
    Affected if The macOS version is 13.0 through 13.3.x (any version >= 13.0 but < 13.4)
  3. Check the installed Safari version
    Open Safari > About Safari, or check the Safari version in Applications folder info. Compare against 16.5.
    Affected if Safari version is lower than 16.5 (any version < 16.5)
  4. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and note the version number (e.g., 16.4, 16.5).
    Affected if The iOS/iPadOS version is >= 16.0 but < 16.5 (e.g., 16.0, 16.1, 16.2, 16.3, 16.4)
  5. Check tvOS or watchOS version
    On Apple TV, go to Settings > General > About to see tvOS version. On Apple Watch, open the Settings app on the watch, go to General > About to see watchOS version.
    Affected if tvOS version is < 16.5 or watchOS version is < 9.5

The environment is affected if any device or browser listed is running a version lower than the minimum fixed version (macOS 13.4, Safari 16.5, iOS/iPadOS 16.5, tvOS 16.5, or watchOS 9.5).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.5 / 13.4 / 16.5 or later
Fixed in 9.513.416.5
Interim mitigation

Apply the available security updates (watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, Safari 16.5, iOS 16.5, iPadOS 16.5 or later) to all affected devices and systems.

Recommended fix High confidence

iOS 16.5, iPadOS 16.5, macOS Ventura 13.4, Safari 16.5, tvOS 16.5, watchOS 9.5

  1. Identify the affected Apple product (Safari, iOS, iPadOS, macOS, tvOS, or watchOS) from the deployed environment
  2. Check the current installed version of the product
  3. For iOS devices: Upgrade to iOS 16.5 or later via Settings > General > Software Update
  4. For iPadOS tablets: Upgrade to iPadOS 16.5 or later via Settings > General > Software Update
  5. For macOS systems: Upgrade to macOS Ventura 13.4 or later via System Preferences > Software Update
  6. For Safari browser: Upgrade to Safari 16.5 or later (included with macOS 13.4 update)
  7. For Apple TV: Upgrade to tvOS 16.5 or later via Settings > System > Software Updates
  8. For Apple Watch: Upgrade to watchOS 9.5 or later via the Watch app on iPhone
Caveat Apple minor version updates typically include compatibility improvements; some older applications or configurations may need updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32402 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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