dbcve.org
macOSOperating system · Apple

CVE-2024-40807

MEDIUM · 5.5 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 →
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
A logic issue was addressed with improved checks. This issue is fixed in macOS Monterey 12.7.6, macOS Sonoma 14.6, macOS Ventura 13.6.8. A shortcut may be able to use sensitive data with certain actions without prompting the user.

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 logic flaw in macOS Shortcuts allowed shortcuts to access sensitive data through certain actions without triggering user prompts, bypassing the normal privacy consent mechanism. The vulnerability existed due to insufficient validation checks before permitting sensitive data access.

MitigationApply the appropriate macOS security update (Monterey 12.7.6, Ventura 13.6.8, or Sonoma 14.6) to address the logic issue and restore proper user prompting for sensitive data access by shortcuts.

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:< 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
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 your macOS version
    Open Terminal and run: sw_vers -productVersion
    Affected if The version is 12.7.5 or earlier, 13.0 through 13.6.7, or 14.0 through 14.5 (these are the vulnerable versions)
  2. Confirm macOS Monterey version
    If running macOS 12.x, check that the minor version is 12.7.6 or later via: sw_vers -productVersion
    Affected if Running Monterey 12.7.5 or earlier indicates vulnerability
  3. Confirm macOS Ventura version
    If running macOS 13.x, verify the version is 13.6.8 or later via: sw_vers -productVersion
    Affected if Running Ventura 13.0 through 13.6.7 indicates vulnerability
  4. Confirm macOS Sonoma version
    If running macOS 14.x, verify the version is 14.6 or later via: sw_vers -productVersion
    Affected if Running Sonoma 14.0 through 14.5 indicates vulnerability
  5. Identify Shortcuts with sensitive data access
    Open Shortcuts app, review any shortcuts that access contacts, photos, calendars, reminders, or other sensitive categories
    Affected if You have shortcuts that access sensitive data while running a vulnerable macOS version

You are affected if your macOS version falls within the vulnerable ranges (Monterey <12.7.6, Ventura 13.0-13.6.7, or Sonoma 14.0-14.5) and you use Shortcuts that access sensitive information.

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

Apply the appropriate macOS security update (Monterey 12.7.6, Ventura 13.6.8, or Sonoma 14.6) to address the logic issue and restore proper user prompting for sensitive data access by shortcuts.

Recommended fix High confidence

macOS Monterey 12.7.6 / macOS Ventura 13.6.8 / macOS Sonoma 14.6 (depending on your current OS version)

  1. Identify the currently installed macOS version by clicking the Apple menu and selecting About This Mac
  2. Determine which macOS upgrade path applies based on your current version (Monterey 12.x, Ventura 13.x, or Sonoma 14.x)
  3. For macOS Monterey (12.x) users: Upgrade to macOS 12.7.6 or later via System Settings > General > Software Update
  4. For macOS Ventura (13.x) users: Upgrade to macOS 13.6.8 or later via System Settings > General > Software Update
  5. For macOS Sonoma (14.x) users: Upgrade to macOS 14.6 or later via System Settings > General > Software Update
  6. Alternatively, download the appropriate macOS installer from the Mac App Store and perform a clean install or upgrade
  7. After upgrading, verify the update was successful by checking About This Mac for the version number
Caveat Standard macOS upgrade considerations apply - some legacy applications may not be compatible with newer macOS versions, and certain system settings may need to be reconfigured after upgrade

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

Fix this in macOS Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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