macOSOperating system · Apple

CVE-2024-40797

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 13.7 / 14.7 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
This issue was addressed through improved state management. This issue is fixed in macOS Sequoia 15, macOS Sonoma 14.7, macOS Ventura 13.7. Visiting a malicious website may lead to user interface 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 · moderate confidence

A state management vulnerability in macOS WebKit allows malicious websites to spoof user interface elements. The vulnerability is triggered when a user visits a crafted website, potentially tricking them into believing they're interacting with legitimate UI components.

MitigationUpdate macOS to version 15 (Sequoia), 14.7 (Sonoma), or 13.7 (Ventura) or later to receive the state management fix. Avoid visiting untrusted websites until the update is applied.

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
macOSOperating system
Affected:< 13.7>= 14.0, < 14.7

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 installed macOS version
    Open Terminal and run: sw_vers -productVersion
    Affected if The version displayed is below 13.7, or between 14.0 and 14.6 (inclusive)
  2. Confirm macOS release name
    Run: sw_vers -productVersionExtra to see if it shows Ventura, Sonoma, or Sequoia, or check System Settings > About
    Affected if Running Ventura versions before 13.7, or Sonoma versions before 14.7, or any version below 13.7 regardless of name
  3. Identify WebKit-based browsers in use
    Check for Safari, or any third-party browsers that use WebKit (common on macOS). Look in /Applications folder or run: defaults read /Applications/Safari.app/Contents/Info CFBundleIdentifier
    Affected if WebKit-based browsers are installed and used, combined with a vulnerable macOS version from steps 1-2
  4. Verify Safari WebKit engine
    Open Safari, go to Safari > Settings > Advanced, enable Show Develop menu, then Develop > WebKit Version in menu bar
    Affected if The WebKit version cannot be separately checked on macOS - the vulnerability is tied to macOS version, not separate WebKit version

If macOS version is 13.7 or higher, 14.7 or higher, or 15 (Sequoia) or higher, the environment is NOT affected; any version below 13.7 or between 14.0 and 14.6 IS affected when using WebKit-based browsers.

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 13.7 / 14.7 or later
Fixed in 13.714.7
Interim mitigation

Update macOS to version 15 (Sequoia), 14.7 (Sonoma), or 13.7 (Ventura) or later to receive the state management fix. Avoid visiting untrusted websites until the update is applied.

Recommended fix High confidence

macOS Ventura 13.7, macOS Sonoma 14.7, or macOS Sequoia 15

  1. Identify your current macOS version by clicking the Apple menu and selecting 'About This Mac'
  2. Back up important data before performing any system update
  3. Determine which upgrade path applies based on your current version: If running macOS Ventura (13.x), update to 13.7 or later; If running macOS Sonoma (14.0-14.6), update to 14.7 or later; If running macOS Sequoia (15.x), no action needed as it is already fixed
  4. Open System Settings > General > Software Update to check for and install the available update
  5. Restart your Mac if prompted to complete the installation
Caveat Standard macOS update considerations apply - verify application compatibility with new OS version before deploying in production environments

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

Fix this in macOS 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-40797 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-40797 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