dbcve.org
SafariWeb browser · Apple

CVE-2024-44212

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 2.1 / 11.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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.1, iOS 18.1 and iPadOS 18.1, macOS Sequoia 15.1, tvOS 18.1, visionOS 2.1, watchOS 11.1. Cookies belonging to one origin may be sent to another 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 · high confidence

A cookie management flaw in WebKit allowed cookies from one origin to be incorrectly sent to a different origin, violating the Same-Origin Policy. This cross-origin cookie leakage could enable session hijacking or information disclosure between sites.

MitigationApply the vendor patches: Safari 18.1, iOS 18.1/iPadOS 18.1, macOS Sequoia 15.1, tvOS 18.1, visionOS 2.1, or watchOS 11.1. No additional configuration required.

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.1
IpadosOperating system
Affected:< 18.1
Iphone OsOperating system
Affected:< 18.1
TvosOperating system
Affected:< 18.1
VisionosOperating system
Affected:< 2.1
WatchosOperating system
Affected:< 11.1

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 running WebKit
    Determine if the device runs Safari, iOS, iPadOS, tvOS, visionOS, or watchOS. Check the device model and operating system name.
    Affected if The device runs any of the affected WebKit-based Apple products
  2. Check the installed Safari version
    Open Safari, go to Safari > About Safari (macOS) or Settings > Safari > About (iOS/iPadOS). Record the version number shown.
    Affected if The version displayed is earlier than 18.1
  3. Check the iOS or iPadOS version
    Go to Settings > General > About on the device. Record the iOS or iPadOS version number.
    Affected if The version is earlier than 18.1
  4. Check the tvOS version
    Go to Settings > General > About on Apple TV. Record the tvOS version number.
    Affected if The version is earlier than 18.1
  5. Check the watchOS version
    Open the Watch app on iPhone, go to My Watch > General > About. Record the watchOS version number.
    Affected if The version is earlier than 11.1
  6. Check the visionOS version
    Go to Settings > General > About on Apple Vision Pro. Record the visionOS version number.
    Affected if The version is earlier than 2.1

If the installed OS version or Safari version is below 18.1 (or below 2.1 for visionOS, or below 11.1 for watchOS), the WebKit cookie handling flaw is present and cross-origin cookies may be incorrectly sent between sites.

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.1 / 11.1 / 18.1 or later
Fixed in 2.111.118.1
Interim mitigation

Apply the vendor patches: Safari 18.1, iOS 18.1/iPadOS 18.1, macOS Sequoia 15.1, tvOS 18.1, visionOS 2.1, or watchOS 11.1. No additional configuration required.

Recommended fix High confidence

Safari 18.1, iOS 18.1, iPadOS 18.1, tvOS 18.1, visionOS 2.1, watchOS 11.1, macOS Sequoia 15.1

  1. Update Safari to version 18.1 or later
  2. Update iOS (iPhone) to version 18.1 or later
  3. Update iPadOS to version 18.1 or later
  4. Update tvOS to version 18.1 or later
  5. Update visionOS to version 2.1 or later
  6. Update watchOS to version 11.1 or later
  7. Update macOS to Sequoia 15.1 or later (which includes the Safari fix)
Caveat Standard OS/software update considerations apply; ensure backups 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
  • Testing1.0 h
  • Review / QA1.0 h
3.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-44212 — 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-44212 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