SafariWeb browser · Apple

CVE-2024-23263

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-08

Fix available

A fix is available. Upgrade to 1.1 / 10.4 or later.

See remediation →

72/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

A logic issue was addressed with improved validation. This issue is fixed in Safari 17.4, iOS 16.7.6 and iPadOS 16.7.6, iOS 17.4 and iPadOS 17.4, macOS Sonoma 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4. Processing maliciously crafted web content may prevent Content Security Policy from being enforced.

Technical summary

dbcve analysis · high confidence

A logic flaw in WebKit allows maliciously crafted web content to bypass Content Security Policy (CSP) enforcement, potentially enabling XSS and data injection attacks. CSP is a critical HTTP header that controls which resources can be loaded, and bypassing it undermines web application security.

MitigationUpdate affected Apple products to the fixed versions: Safari 17.4, iOS/iPadOS 17.4 or 16.7.6, macOS Sonoma 14.4, tvOS 17.4, visionOS 1.1, or watchOS 10.4.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

SafariWeb browser

Affected:< 17.4

FedoraOperating system

Affected:= 38= 39= 40

IpadosOperating system

Affected:< 16.7.6>= 17.0, < 17.4

Iphone OsOperating system

Affected:< 16.7.6>= 17.0, < 17.4

macOSOperating system

Affected:>= 14.0, < 14.4

TvosOperating system

Affected:< 17.4

VisionosOperating system

Affected:< 1.1

WatchosOperating system

Affected:< 10.4

CVSS breakdown

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?

dbcve checks

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

Identify the browser and platform

Determine if you are using Safari on Apple devices or a WebKit-based browser on Fedora (such as Epiphany, GNOME Web, or Midori). On macOS, Safari is the primary WebKit browser. On iOS/iPadOS, all browsers use WebKit due to platform restrictions.

Affected if You are using Safari or any WebKit-based browser on the listed platforms.
Check Safari version on macOS

Open Safari, go to Safari menu > About Safari. Compare the version number to the affected range: macOS 14.0 to 14.3 are vulnerable. If running macOS 14.4 or later, you are not affected.

Affected if Safari version corresponds to macOS versions earlier than 14.4.
Check iOS or iPadOS version

Go to Settings > General > About on your iPhone or iPad. Note the iOS version. Affected versions are: any version before 16.7.6, or versions 17.0 through 17.3.

Affected if iOS/iPadOS version is less than 16.7.6, or falls between 17.0 and 17.3 inclusive.
Check Safari version on iOS/iPadOS

Open Settings > Safari > About. The Safari version matches the iOS version on iOS 17+ or is tied to the iOS version on iOS 16. Use the iOS version check in step 3 instead.

Affected if iOS/iPadOS version is in the affected range as described in step 3.
Check tvOS, visionOS, or watchOS version

On Apple TV, go to Settings > General > About. On Apple Watch, open the Watch app on iPhone > General > About. On Apple Vision Pro, go to Settings > General > About. Affected: tvOS versions before 17.4, visionOS before 1.1, watchOS before 10.4.

Affected if tvOS is earlier than 17.4, visionOS is earlier than 1.1, or watchOS is earlier than 10.4.
Check WebKitGTK version on Fedora

For WebKitGTK-based browsers on Fedora 38, 39, or 40, check the webkit2gtk package version using: rpm -qa | grep -i webkit2gtk. Compare the installed version against the package updates for your Fedora version.

Affected if Running Fedora 38, 39, or 40 with WebKitGTK browsers and the WebKit package has not been updated to include the CVE fix.

You are affected if you are running any Safari version on macOS 14.0-14.3, iOS/iPadOS 16.7.5 or earlier or 17.0-17.3, tvOS before 17.4, visionOS before 1.1, watchOS before 10.4, or Fedora 38/39/40 with unpatched WebKitGTK.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.1 / 10.4 / 14.4 or later

Fixed in 1.110.414.4

Interim mitigation

Update affected Apple products to the fixed versions: Safari 17.4, iOS/iPadOS 17.4 or 16.7.6, macOS Sonoma 14.4, tvOS 17.4, visionOS 1.1, or watchOS 10.4.

Recommended fix High confidence

Upgrade to Safari 17.4, iOS/iPadOS 17.4 (or 16.7.6), macOS Sonoma 14.4, tvOS 17.4, visionOS 1.1, or watchOS 10.4 as appropriate for your device

For iOS/iPadOS: Go to Settings > General > Software Update and upgrade to iOS/iPadOS 17.4 (or 16.7.6 for older devices)
For macOS: Go to System Settings > General > Software Update and upgrade to macOS Sonoma 14.4
For Safari (macOS): Ensure Safari is updated as part of macOS 14.4 system update
For tvOS: Go to Settings > General > Apple TV Software Update and upgrade to tvOS 17.4
For watchOS: On iPhone, open Watch app > General > Software Update and upgrade to watchOS 10.4
For visionOS: Go to Settings > General > Software Update and upgrade to visionOS 1.1
For Fedora: Run 'sudo dnf update webkit2gtk' to obtain the patched package for versions 38, 39, or 40

Caveat Standard OS update considerations apply (backup data, ensure compatibility with critical applications)

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-2024-23263 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2024-23263?

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.

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

At a glance

A fix existsUpgrade to 1.1 / 10.4 or later

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 1.5%

Affects: Safari

Remediation

Need this fixed?

Fix this in Safari 9 hrs · Low

Typical engagement from $1,600

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-23263 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References