CVE-2024-23201
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 · uneditedA permissions issue was addressed with additional restrictions. This issue is fixed in iOS 17.3 and iPadOS 17.3, macOS Monterey 12.7.4, macOS Sonoma 14.3, macOS Ventura 13.6.5, tvOS 17.3, watchOS 10.3. An app may be able to cause a denial-of-service.
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 confidenceThis is a permissions bypass vulnerability in Apple operating systems where an application can exploit insufficient access controls to cause a denial-of-service condition. The fix involved implementing additional restrictions to properly enforce permission boundaries.
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.3< 17.3>= 12.0, < 12.7.4>= 13.0, < 13.6.5>= 14.0, < 14.3< 17.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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
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.
-
Check macOS versionRun 'sw_vers -productVersion' in Terminal to get the installed macOS versionAffected if The version is 12.0 through 12.7.3, 13.0 through 13.6.4, or 14.0 through 14.2 (any build before 12.7.4, 13.6.5, or 14.3)
-
Check iOS versionOn the device, go to Settings > General > About to view the iOS version numberAffected if The version is any build before 17.3 (e.g., 17.2.x, 17.1.x, etc.)
-
Check iPadOS versionOn the iPad, go to Settings > General > About to view the iPadOS version numberAffected if The version is any build before 17.3 (e.g., 17.2.x, 17.1.x, etc.)
-
Check tvOS versionOn Apple TV, go to Settings > General > About to view the tvOS version numberAffected if The version is any build before 17.3 (e.g., 17.2.x, 17.1.x, etc.)
-
Check watchOS versionOn Apple Watch, open the Settings app > General > About to view the watchOS version numberAffected if The version is any build before 10.3 (e.g., 10.2.x, 10.1.x, etc.)
The environment is affected if any Apple device runs an OS version lower than the minimum fixed version (iOS/iPadOS/tvOS/watchOS below 17.3/10.3, or macOS below 12.7.4/13.6.5/14.3 depending on the major version).
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.312.7.413.6.5
Apply the vendor-supplied OS updates (iOS 17.3+, iPadOS 17.3+, macOS Monterey 12.7.4+, macOS Sonoma 14.3+, macOS Ventura 13.6.5+, tvOS 17.3+, watchOS 10.3+) to affected devices.
Upgrade to iOS/iPadOS 17.3, macOS 12.7.4/13.6.5/14.3, tvOS 17.3, or watchOS 10.3 depending on device type and current version
- Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, or Apple Watch)
- Check the current operating system version in Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
- Back up important data using iCloud or Finder/iTunes as a precaution before applying updates
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 17.3
- For Mac: Go to System Settings > General > Software Update and install the appropriate macOS version (12.7.4, 13.6.5, or 14.3 depending on your current macOS)
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.3
- For Apple Watch: On your iPhone, open the Watch app, go to My Watch > General > Software Update and install watchOS 10.3
- Restart the device after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23201 — 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
- support.apple.com
- 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
- 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-23201 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