dbcve.org
SafariWeb browser · Apple

CVE-2023-27954

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-08
Fix available
A fix is available. Upgrade to 9.4 / 13.3 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
The issue was addressed by removing origin information. This issue is fixed in macOS Ventura 13.3, Safari 16.4, iOS 16.4 and iPadOS 16.4, iOS 15.7.4 and iPadOS 15.7.4, tvOS 16.4, watchOS 9.4. A website may be able to track sensitive user 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 · moderate confidence

This is a WebKit/Safari vulnerability where a malicious website could track sensitive user information through origin information leakage. The fix involved removing origin information, suggesting improper handling of origin headers or similar web security mechanisms that allowed cross-origin information disclosure.

MitigationUpdate to the fixed versions: Safari 16.4+, iOS 15.7.4+/16.4+, iPadOS 15.7.4+/16.4+, macOS Ventura 13.3+, tvOS 16.4+, or watchOS 9.4+.

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.4
Debian LinuxOperating system
Affected:= 10.0
IpadosOperating system
Affected:< 15.7.4>= 16.0, < 16.4
Iphone OsOperating system
Affected:< 15.7.4>= 16.0, < 16.4
macOSOperating system
Affected:>= 13.0, < 13.3
TvosOperating system
Affected:< 16.4
WatchosOperating system
Affected:< 9.4

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 WebKit-based browser in use
    Determine if Safari, or any WebKit-based browser on Apple devices or Debian is being used. On macOS, Safari is the primary WebKit browser. On iOS/iPadOS, Safari and some third-party browsers use WebKit. On Debian Linux, check for webkit2gtk packages.
    Affected if The browser or underlying WebKit component is from an affected product and version range.
  2. Check Safari version on macOS
    Open Safari, go to Safari menu > About Safari, or check the version in System Settings > Privacy & Security > Safari > About Safari. Compare the version number to the affected range: anything less than 16.4, or between 13.0 and 13.3.
    Affected if Safari version is < 16.4, or falls between 13.0 and 13.3 inclusive.
  3. Check Safari version on iOS or iPadOS
    Open Settings app, go to Settings > Safari > About, or go to Settings > General > About. Note the iOS/iPadOS version and Safari version if shown.
    Affected if iOS/iPadOS version is < 15.7.4, or >= 16.0 but < 16.4.
  4. Check tvOS or watchOS version
    On Apple TV, go to Settings > General > About. On Apple Watch, open the Watch app on iPhone and go to General > About.
    Affected if tvOS version is < 16.4, or watchOS version is < 9.4.
  5. Check WebKitGTK version on Debian Linux 10.0
    Run 'dpkg -l | grep -i webkit' or 'apt show libwebkit2gtk-4.0-37' (or similar webkit package) to determine the installed WebKit version.
    Affected if WebKitGTK version is present and matches the Debian 10.0 package version, indicating the unpatched variant.

The environment is affected if Safari, iOS, iPadOS, macOS, tvOS, watchOS, or Debian Linux 10.0 WebKit is running a version lower than the fixed releases (Safari 16.4+, iOS/iPadOS 15.7.4+/16.4+, macOS Ventura 13.3+, tvOS 16.4+, watchOS 9.4+).

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.4 / 13.3 / 15.7.4 or later
Fixed in 9.413.315.7.4
Interim mitigation

Update to the fixed versions: Safari 16.4+, iOS 15.7.4+/16.4+, iPadOS 15.7.4+/16.4+, macOS Ventura 13.3+, tvOS 16.4+, or watchOS 9.4+.

Recommended fix High confidence

macOS Ventura 13.3, Safari 16.4, iOS/iPadOS 16.4 or 15.7.4, tvOS 16.4, watchOS 9.4

  1. Identify the Apple device and current OS version using Settings > General > About (iOS/iPadOS) or System Preferences > General (macOS)
  2. For iPhone/iPad: Upgrade to iOS/iPadOS 16.4 or later, or iOS/iPadOS 15.7.4 if staying on major version 15
  3. For Mac: Upgrade to macOS Ventura 13.3 or later
  4. For Safari browser on older macOS: Upgrade to Safari 16.4
  5. For Apple TV: Upgrade to tvOS 16.4 or later
  6. For Apple Watch: Upgrade to watchOS 9.4 or later
  7. After upgrade, verify the version in Settings > General > About to confirm the fix is applied

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
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27954 — 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-27954 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