dbcve.org
macOSOperating system · Apple

CVE-2024-40847

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 13.7 / 14.7 or later.
See remediation →
57/100
Remediation priority · Elevated
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
The issue was addressed with additional code-signing restrictions. This issue is fixed in macOS Sequoia 15, macOS Sonoma 14.7, macOS Ventura 13.7. An app may be able to access sensitive user data.

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 · low confidence

This vulnerability involved a code-signing validation issue in macOS that allowed an application to bypass restrictions and access sensitive user data. The fix implemented additional code-signing restrictions to prevent unauthorized access to protected user information.

MitigationApply the macOS security updates: upgrade to macOS Sequoia 15, Sonoma 14.7, Ventura 13.7 or later. Organizations should ensure all managed macOS devices are patched to these versions.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 installed macOS version
    Run 'sw_vers -productVersion' in Terminal or go to System Settings > About to view the macOS version
    Affected if The version is less than 13.7, or is 14.0 through 14.6 (any version in the range >= 14.0 and < 14.7)
  2. Identify macOS release name
    Run 'sw_vers -productVersion' and note whether it shows 13.x (Ventura) or 14.x (Sonoma)
    Affected if Running Ventura 13.x versions below 13.7, or Sonoma 14.x versions below 14.7
  3. Confirm code signing status
    Check if Gatekeeper is enabled by running 'spctl --status' in Terminal
    Affected if Code signing validation is disabled (Gatekeeper off), making the bypass possible if the OS version is vulnerable

You are affected if your macOS version is 13.7 or higher (Ventura 13.7+, Sonoma 14.7+, or Sequoia 15+); otherwise, the code-signing bypass vulnerability is present.

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

Apply the macOS security updates: upgrade to macOS Sequoia 15, Sonoma 14.7, Ventura 13.7 or later. Organizations should ensure all managed macOS devices are patched to these versions.

Recommended fix High confidence

macOS Ventura 13.7, macOS Sonoma 14.7, or macOS Sequoia 15 (depending on current major version)

  1. Back up your Mac using Time Machine or another backup solution
  2. If running macOS Ventura (13.x), upgrade to macOS Ventura 13.7
  3. If running macOS Sonoma (14.x), upgrade to macOS Sonoma 14.7
  4. If running macOS Sequoia (15.x), upgrade to macOS Sequoia 15
  5. Restart your Mac after the update completes
  6. Verify the update was successful by checking System Settings > General > Software Update

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

Fix this in macOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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