dbcve.org
SafariWeb browser · Apple

CVE-2024-23280

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-08
Fix available
A fix is available. Upgrade to 2.44.0 / 10.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 injection issue was addressed with improved validation. This issue is fixed in Safari 17.4, iOS 17.4 and iPadOS 17.4, macOS Sonoma 14.4, tvOS 17.4, watchOS 10.4. A maliciously crafted webpage may be able to fingerprint the user.

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 an injection vulnerability in WebKit (Apple's browser engine) that allows a maliciously crafted webpage to fingerprint users. The vulnerability was addressed with improved input validation. User fingerprinting enables tracking across websites without consent.

MitigationUpdate all affected Apple devices to iOS 17.4+, iPadOS 17.4+, macOS Sonoma 14.4+, tvOS 17.4+, watchOS 10.4+, or Safari 17.4+ to receive the 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.4
FedoraOperating system
Affected:= 38= 39= 40
Ipad OsOperating system
Affected:< 17.4
Iphone OsOperating system
Affected:< 17.4
macOSOperating system
Affected:>= 14.0, < 14.4
TvosOperating system
Affected:< 17.4
WatchosOperating system
Affected:< 10.4
WebkitgtkWeb browser
Affected:< 2.44.0

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 > About Safari, or run: defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString
    Affected if version is present and less than 17.4
  2. Check iOS or iPadOS version on Apple mobile devices
    Open Settings > General > About and note the version number
    Affected if version is less than 17.4
  3. Check macOS version on Mac computers
    Click Apple menu > About This Mac
    Affected if macOS version is 14.0 through 14.3.x (inclusive)
  4. Check tvOS version on Apple TV
    Open Settings > General > About > Version
    Affected if version is less than 17.4
  5. Check watchOS version on Apple Watch
    Open Settings > General > About on the paired iPhone, or go to General > About on the Watch
    Affected if version is less than 10.4
  6. Check WebKitGTK version on Linux/Fedora systems
    Run: rpm -qa | grep webkit2gtk or dpkg -l | grep webkit2gtk to list installed WebKit packages and their versions
    Affected if webkit2gtk version is less than 2.44.0

A user is affected if their Safari is below 17.4, iOS/iPadOS below 17.4, macOS between 14.0 and 14.3, tvOS below 17.4, watchOS below 10.4, or WebKitGTK below 2.44.0.

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 2.44.0 / 10.4 / 14.4 or later
Fixed in 2.44.010.414.4
Interim mitigation

Update all affected Apple devices to iOS 17.4+, iPadOS 17.4+, macOS Sonoma 14.4+, tvOS 17.4+, watchOS 10.4+, or Safari 17.4+ to receive the fix.

Recommended fix High confidence

Safari 17.4, iOS 17.4, iPadOS 17.4, macOS 14.4, tvOS 17.4, watchOS 10.4, or WebKitGTK 2.44.0

  1. For Apple devices: Upgrade to iOS 17.4, iPadOS 17.4, macOS Sonoma 14.4, tvOS 17.4, or watchOS 10.4 as appropriate for your device
  2. For Safari: Upgrade to Safari 17.4
  3. For WebKitGTK-based systems (including Fedora): Update webkit2gtk to version 2.44.0 or later via your system's package manager (e.g., 'dnf update webkit2gtk' on Fedora)
Caveat Standard OS/application update risks apply - review release notes for your specific platform before updating

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

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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