dbcve.org
SafariWeb browser · Apple

CVE-2024-44187

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 2.0 / 11.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 cross-origin issue existed with "iframe" elements. This was addressed with improved tracking of security origins. 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 · high confidence

This is a cross-origin policy bypass vulnerability in WebKit/Safari affecting iframe elements. The browser failed to properly track security origins, allowing a malicious website to embed legitimate sites in iframes and exfiltrate data across origins. This is a Same-Origin Policy implementation flaw.

MitigationUpdate all affected Apple devices to Safari 18, iOS 18, iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, or watchOS 11 and later. For web applications, implement X-Frame-Options: DENY or SAMEORIGIN and Content-Security-Policy: frame-ancestors directives as defense-in-depth.

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
VisionosOperating system
Affected:< 2.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. Check Safari version on macOS
    Open Safari, go to Safari > About Safari. Alternatively, run: defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString
    Affected if Version is below 18.0 (e.g., 17.x or earlier)
  2. Check iOS or iPadOS Safari version
    Open Settings app, tap Safari, scroll down and tap About. The version number appears next to 'Version'
    Affected if Version is below 18.0 (e.g., 17.x or earlier)
  3. Check macOS version as Safari version is tied to OS
    Open System Settings > About, or run: sw_vers -productVersion in Terminal
    Affected if macOS version is below 15.0 (e.g., 14.x or earlier) - Safari bundled with these versions is affected regardless of Safari's standalone version number
  4. Check WebKit version via JavaScript (for embedded browsers)
    Open the browser and run in console: navigator.userAgent or navigator.appVersion to identify WebKit version; cross-reference with WebKit release notes for version containing the fix
    Affected if WebKit version predates the security fix (earlier than Safari 18/WebKit releases from late 2024)
  5. Verify Same-Origin Policy enforcement on your site
    Host a test page with an iframe pointing to a different origin (or a test subdomain), then attempt to access iframe.contentWindow.location or document.cookie from the parent page via JavaScript
    Affected if The script can read iframe location or cross-origin data without throwing a DOMException - this indicates the SOP bypass is present

A user is affected if they are running any Safari/WebKit version on iOS, iPadOS, macOS, tvOS, visionOS, or watchOS that is older than the fixed versions (iOS/iPadOS/tvOS/watchOS < 18.0, visionOS < 2.0, macOS < 15.0) and the browser allows cross-origin iframe access that should be blocked by Same-Origin Policy.

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.0 / 11.0 / 15.0 or later
Fixed in 2.011.015.0
Interim mitigation

Update all affected Apple devices to Safari 18, iOS 18, iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, or watchOS 11 and later. For web applications, implement X-Frame-Options: DENY or SAMEORIGIN and Content-Security-Policy: frame-ancestors directives as defense-in-depth.

Recommended fix High confidence

Upgrade to Safari 18, iOS 18, iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, or watchOS 11 depending on device

  1. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 18 or iPadOS 18
  2. For Mac: Go to 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 > General > Software Update and install tvOS 18
  5. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2
  6. For Safari on older macOS: Upgrade to macOS Sequoia 15 which includes Safari 18
Caveat Security updates typically have minimal breaking changes; however, some legacy web features or older website compatibility may be affected by the security origin tracking improvements

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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