dbcve.org
SafariWeb browser · Apple

CVE-2024-54467

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-10
Fix available
A fix is available. Upgrade to 11.0 / 15.0 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 cookie management issue was addressed with improved state management. This issue is fixed in Safari 18, iOS 18 and iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, watchOS 11. A malicious website may exfiltrate data cross-origin.

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 cookie state management vulnerability in WebKit that allows a malicious website to exfiltrate data across origins by improperly accessing or manipulating cookies that should be restricted by same-origin policy. The vulnerability enables cross-origin data theft through flawed cookie handling in Safari and other Apple browser engines.

MitigationApply the available vendor updates (Safari 18, iOS 18, iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, watchOS 11) to all affected devices and browsers to resolve the cookie state management flaw.

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:< 18.0
IpadosOperating system
Affected:< 18.0
Iphone OsOperating system
Affected:< 18.0
macOSOperating system
Affected:< 15.0
TvosOperating system
Affected:< 18.0
WatchosOperating system
Affected:< 11.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
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 and browser in use
    Determine if the user is running Safari on macOS, Safari on iOS/iPadOS, or any browser using WebKit on Apple devices. Note the specific device type (iPhone, iPad, Mac, Apple Watch, Apple TV).
    Affected if The product is any Apple browser or WebKit-based browser on the listed platforms.
  2. Check Safari version on macOS
    Open Safari, select Safari menu, choose About Safari, and note the version number displayed (e.g., 17.x, 18.0).
    Affected if The Safari version is earlier than 18.0 on macOS.
  3. Check iOS or iPadOS version
    Go to Settings > General > About on the iPhone or iPad, and note the version number (e.g., 17.x, 18.0).
    Affected if The iOS or iPadOS version is earlier than 18.0.
  4. Check macOS version
    Go to System Settings > General > About on Mac, and note the version number (e.g., 14.x, 15.0).
    Affected if The macOS version is earlier than 15.0.
  5. 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. Note the version number.
    Affected if The tvOS version is earlier than 18.0 or watchOS version is earlier than 11.0.

The user is affected if they are running any Safari browser or Apple device with an OS version lower than 18.0 (iOS/iPadOS/tvOS/Safari), 15.0 (macOS), or 11.0 (watchOS), as these versions contain the fixed WebKit cookie state management.

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 11.0 / 15.0 / 18.0 or later
Fixed in 11.015.018.0
Interim mitigation

Apply the available vendor updates (Safari 18, iOS 18, iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, watchOS 11) to all affected devices and browsers to resolve the cookie state management flaw.

Recommended fix High confidence

Safari 18, iOS 18, iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, watchOS 11

  1. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 18 or iPadOS 18
  2. For Mac: Open System Settings > General > Software Update and install macOS Sequoia 15
  3. For Apple Watch: Open the Watch app on iPhone, go to General > Software Update, and install watchOS 11
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 18
  5. For Safari on older macOS: Upgrade to macOS Sequoia 15 which includes Safari 18
  6. For visionOS: Upgrade to visionOS 2 via Settings > Software Update
Caveat Major OS upgrades may have app compatibility implications; review app compatibility before upgrading

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-54467 — 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-54467 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