CVE-2024-23204
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 · uneditedThe issue was addressed with additional permissions checks. This issue is fixed in iOS 16.7.6 and iPadOS 16.7.6, iOS 17.3 and iPadOS 17.3, macOS Monterey 12.7.4, macOS Sonoma 14.3, macOS Ventura 13.6.5, watchOS 10.3. 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 · moderate confidenceA vulnerability in Apple's Shortcuts application allowed shortcuts to access sensitive data without proper user permission prompts due to insufficient permissions checks. The fix implemented additional permission checks to ensure user consent is required before sensitive data can be accessed by shortcut actions.
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> 17.0, < 17.3> 17.0, < 17.3< 14.3< 10.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Apple device and operating systemDetermine whether you are using an iPhone, iPad, Mac, or Apple Watch. On iPhone/iPad, go to Settings > General > About to see the iOS/iPadOS version. On Mac, go to System Settings > About to see the macOS version. On Apple Watch, open the Settings app on the watch and go to General > About to see watchOS version.Affected if The device runs an affected OS version (iOS/iPadOS > 17.0 and < 17.3, macOS < 14.3, or watchOS < 10.3)
-
Verify iOS or iPadOS version on iPhone or iPadGo to Settings > General > About and note the version number. Compare it to the affected range: greater than 17.0 and less than 17.3.Affected if The iOS or iPadOS version shows a number like 17.1, 17.1.x, 17.2, or 17.2.x (any version between 17.1 and 17.2.x inclusive)
-
Verify macOS version on MacGo to System Settings > About (or Apple menu > About This Mac on older macOS) and note the macOS version number. Compare to 14.3.Affected if The macOS version is earlier than 14.3 (such as 14.2, 14.1, 14.0, or any version of Ventura 13.x or Monterey 12.x)
-
Verify watchOS version on Apple WatchOn the Apple Watch, open the Settings app, scroll to General, tap About, and note the watchOS version. Compare to 10.3.Affected if The watchOS version is earlier than 10.3 (such as 10.2, 10.1, 10.0, or any version of watchOS 9.x)
-
Confirm Shortcuts app presenceThe Shortcuts app is a built-in application on iOS 17+, iPadOS 17+, macOS 12+, and watchOS 10+. Search for Shortcuts in the app library or Launchpad to confirm it is installed.Affected if The Shortcuts app is available on the device, which is the case for all devices running the affected OS versions
You are affected if your device runs iOS/iPadOS 17.1 through 17.2.x, macOS earlier than 14.3, or watchOS earlier than 10.3, and you have access to the Shortcuts application.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.314.317.3
Apply the available security updates to all affected Apple devices: iOS 16.7.6 or later, iPadOS 16.7.6 or later, macOS Monterey 12.7.4 or later, macOS Ventura 13.6.5 or later, macOS Sonoma 14.3 or later, and watchOS 10.3 or later.
iOS 16.7.6 / iPadOS 16.7.6, iOS 17.3 / iPadOS 17.3, macOS Monterey 12.7.4, macOS Ventura 13.6.5, macOS Sonoma 14.3, watchOS 10.3
- Open Settings > General > Software Update on iPhone or iPad
- Download and install the available security update
- For macOS: Open System Settings > General > Software Update and install the update
- For Apple Watch: Open the Watch app on iPhone, go to General > Software Update, and install watchOS 10.3
- After updating, verify the version in Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23204 — 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- support.apple.com
- support.apple.com
- support.apple.com
- seclists.org
- seclists.org
- seclists.org
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- seclists.org
- seclists.org
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23204 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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