CVE-2024-40793
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 · uneditedThis issue was addressed by removing the vulnerable code. This issue is fixed in iOS 16.7.9 and iPadOS 16.7.9, iOS 17.6 and iPadOS 17.6, macOS Monterey 12.7.6, macOS Sonoma 14.6, macOS Ventura 13.6.8, watchOS 10.6. An app may be able to access user-sensitive 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 · moderate confidenceA vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, watchOS) allowed a malicious or compromised application to access user-sensitive data. The issue was resolved by removing the vulnerable code path.
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< 16.7.9>= 17.0, < 17.6< 16.7.9>= 17.0, < 17.6< 12.7.6>= 13.0, < 13.6.8>= 14.0, < 14.6< 10.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS or iPadOS versionOn the device, go to Settings > General > About and note the version number displayed next to 'Version'Affected if The version is earlier than 16.7.9, or is 17.0 through 17.5.x (any version >= 17.0 but < 17.6)
-
Check macOS versionOn the Mac, go to System Settings > About (or System Preferences > About on older macOS) and note the version number displayedAffected if The version is earlier than 12.7.6, or is 13.0 through 13.6.7, or is 14.0 through 14.5.x (any version >= 13.0 but < 13.6.8, or >= 14.0 but < 14.6)
-
Check watchOS versionOn the Apple Watch, open the Settings app, go to General > About and note the version number displayedAffected if The version is earlier than 10.6 (any version < 10.6)
-
Determine if untrusted applications can be installedCheck if the device allows installation of apps from unknown sources (sideloading) or if a malicious app could be installed via MDM or other meansAffected if The device permits installation of applications from sources other than the official App Store without strong vetting, increasing the risk that a malicious app could exploit this vulnerability
The environment is affected if any Apple device (iPhone, iPad, Mac, or Apple Watch) is running an OS version that falls within the affected ranges listed above.
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.612.7.613.6.8
Apply the vendor-supplied security updates: update iOS/iPadOS to 16.7.9 or 17.6, macOS to 12.7.6, 13.6.8, or 14.6, and watchOS to 10.6.
iOS 16.7.9 or iOS 17.6; iPadOS 16.7.9 or iPadOS 17.6; macOS 12.7.6, 13.6.8, or 14.6; watchOS 10.6 depending on current OS
- Open Settings on the device
- Navigate to General > Software Update
- Download and install the available security update for your specific iOS/iPadOS/macOS/watchOS version
- For iOS 16.7.x users: install iOS 16.7.9
- For iOS 17.0-17.5 users: install iOS 17.6
- For iPadOS 16.7.x users: install iPadOS 16.7.9
- For iPadOS 17.0-17.5 users: install iPadOS 17.6
- For macOS Monterey 12.7.x users: install macOS Monterey 12.7.6
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40793 — 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
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- 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
- 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-40793 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