dbcve.org
SafariWeb browser · Apple

CVE-2024-40817

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-29
Fix available
A fix is available. Upgrade to 12.7.6 / 13.6.8 or later.
See remediation →
68/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
The issue was addressed with improved UI handling. This issue is fixed in Safari 17.6, macOS Monterey 12.7.6, macOS Sonoma 14.6, macOS Ventura 13.6.8. Visiting a website that frames malicious content may lead to UI spoofing.

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 UI spoofing vulnerability in Safari's handling of framed content allows malicious websites to overlay or mimic legitimate UI elements, potentially tricking users into performing unintended actions or revealing sensitive information.

MitigationUpdate Safari to version 17.6 or later, or update macOS to the patched versions (Monterey 12.7.6, Ventura 13.6.8, Sonoma 14.6 or later) to remediate this vulnerability.

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.6
macOSOperating system
Affected:>= 12.0, < 12.7.6>= 13.0, < 13.6.8>= 14.0, < 14.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Check Safari version
    Open Safari, then go to Safari > About Safari. Alternatively, run: defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString
    Affected if Version is less than 17.6
  2. Check macOS version
    Click the Apple menu > About This Mac, or run: sw_vers -productVersion
    Affected if Version is 12.0 through 12.7.5, 13.0 through 13.6.7, or 14.0 through 14.5 (these bundled Safari versions are vulnerable)
  3. Identify if Safari is the bundled system browser
    Confirm that the Safari application being used is the system-installed version that ships with macOS, not a third-party or standalone build
    Affected if Using a system-bundled Safari on an affected macOS version

You are affected if Safari version is below 17.6, or if running macOS 12.7.5/13.6.7/14.5 or earlier which ship with vulnerable Safari versions.

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 12.7.6 / 13.6.8 / 14.6 or later
Fixed in 12.7.613.6.814.6
Interim mitigation

Update Safari to version 17.6 or later, or update macOS to the patched versions (Monterey 12.7.6, Ventura 13.6.8, Sonoma 14.6 or later) to remediate this vulnerability.

Recommended fix High confidence

Safari 17.6; macOS Monterey 12.7.6; macOS Ventura 13.6.8; macOS Sonoma 14.6

  1. 1. Identify the current macOS version by clicking the Apple menu > About This Mac
  2. 2. For macOS Monterey (12.x) users: Update to macOS 12.7.6 via System Settings > General > Software Update
  3. 3. For macOS Ventura (13.x) users: Update to macOS 13.6.8 via System Settings > General > Software Update
  4. 4. For macOS Sonoma (14.x) users: Update to macOS 14.6 via System Settings > General > Software Update
  5. 5. For Safari users: Update to Safari 17.6 through the macOS software update or via the App Store updates
Caveat Standard macOS/Safari update - no known breaking changes for this security patch

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