dbcve.org
SafariWeb browser · Apple

CVE-2024-23271

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-24
Fix available
A fix is available. Upgrade to 10.3 / 14.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
A logic issue was addressed with improved checks. This issue is fixed in Safari 17.3, iOS 17.3 and iPadOS 17.3, macOS Sonoma 14.3, tvOS 17.3, watchOS 10.3. A malicious website may cause unexpected cross-origin behavior.

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

A logic flaw in WebKit allows a malicious website to perform unexpected cross-origin actions, potentially bypassing Same-Origin Policy protections. The issue stems from insufficient validation checks that could permit a website to interact with resources or behavior of another origin in ways not intended by the browser security model.

MitigationUpdate all affected Apple products to the patched versions (Safari 17.3, iOS/iPadOS 17.3, macOS Sonoma 14.3, tvOS 17.3, watchOS 10.3) to apply the logic fix.

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:< 17.3
IpadosOperating system
Affected:< 17.3
Iphone OsOperating system
Affected:< 17.3
macOSOperating system
Affected:>= 14.0, < 14.3
TvosOperating system
Affected:< 17.3
WatchosOperating system
Affected:< 10.3

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

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

  1. Check Safari version on macOS
    Open Safari, go to Safari menu > About Safari. Note the version number displayed.
    Affected if Version is lower than 17.3 (for example, 17.2.x or earlier)
  2. Check macOS version on Mac
    Open System Settings > General > About. Note the macOS version number (for example, 14.2, 14.2.1, etc.).
    Affected if macOS version is 14.0, 14.1, or 14.2 (any version 14.0 through 14.2.x), because these correspond to Safari versions before the 17.3 patch
  3. Check iOS or iPadOS version on iPhone or iPad
    Open Settings > General > About. Note the iOS or iPadOS version number (for example, 17.2, 17.2.1).
    Affected if Version is lower than 17.3 (for example, 17.2, 17.2.1, 17.1.x, or any 16.x release)
  4. Check tvOS version on Apple TV
    Go to Settings > General > Apple TV Software Version. Note the version number displayed.
    Affected if Version is lower than 17.3 (for example, 17.2.x or earlier)
  5. Check watchOS version on Apple Watch
    Open the Watch app on iPhone, go to My Watch > General > About. Note the watchOS version number.
    Affected if Version is lower than 10.3 (for example, 10.2.x or earlier)

You are affected if your Safari, iOS, iPadOS, macOS, tvOS, or watchOS version falls within the affected ranges (Safari/iOS/iPadOS/tvOS/watchOS below 17.3/10.3, or macOS 14.0-14.2.x), as these contain the unpatched WebKit logic flaw.

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 10.3 / 14.3 / 17.3 or later
Fixed in 10.314.317.3
Interim mitigation

Update all affected Apple products to the patched versions (Safari 17.3, iOS/iPadOS 17.3, macOS Sonoma 14.3, tvOS 17.3, watchOS 10.3) to apply the logic fix.

Recommended fix High confidence

Safari 17.3, iOS 17.3, iPadOS 17.3, macOS Sonoma 14.3, tvOS 17.3, watchOS 10.3

  1. Check the current version of the affected Apple product (Safari, iOS, iPadOS, macOS, tvOS, or watchOS)
  2. For iOS/iPadOS: Go to Settings > General > Software Update and install iOS/iPadOS 17.3
  3. For macOS: Go to System Settings > General > Software Update and install macOS Sonoma 14.3
  4. For Safari: Update through macOS Sonoma 14.3 or later, or download Safari 17.3 for older macOS versions from Apple
  5. For tvOS: Go to Settings > System > Software Updates and install tvOS 17.3
  6. For watchOS: Go to the Watch app on iPhone > General > Software Update and install watchOS 10.3
  7. Verify the update was successfully applied by checking the version number again
Caveat Standard Apple security update with no major breaking changes expected; may require device restart

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

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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