CVE-2024-27817
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 improved checks. This issue is fixed in iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, macOS Monterey 12.7.5, macOS Sonoma 14.5, macOS Ventura 13.6.7, tvOS 17.5, visionOS 1.2. An app may be able to execute arbitrary code with kernel privileges.
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 confidenceThis is a kernel-level privilege escalation vulnerability affecting multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS). A malicious application could exploit insufficient checks to execute arbitrary code with kernel privileges, effectively gaining complete control over the device.
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.8>= 17.0, < 17.5< 16.7.8>= 17.0, < 17.5< 12.7.5>= 13.0, < 13.6.7>= 14.0, < 14.5< 17.5< 1.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 iOS or iPadOS versionGo to Settings > General > About on the device and note the version number shown next to 'Version'Affected if The version is below 16.7.8, OR between 17.0 and 17.4.x (any version >= 17.0 but < 17.5)
-
Check macOS versionClick the Apple menu > About This Mac and note the version number displayed (such as 13.5 or 14.4)Affected if The version is below 12.7.5, OR between 13.0 and 13.6.6 (any version >= 13.0 but < 13.6.7), OR between 14.0 and 14.4.x (any version >= 14.0 but < 14.5)
-
Check tvOS versionGo to Settings > General > About > Version on Apple TVAffected if The version is any version below 17.5 (that is, < 17.5)
-
Check visionOS versionGo to Settings > General > About on Apple Vision ProAffected if The version is any version below 1.2 (that is, < 1.2)
If the operating system version on your device falls within any of the vulnerable ranges listed above, your device is affected by this kernel privilege escalation vulnerability.
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 · scoped1.212.7.513.6.7
Apply the vendor-supplied patches by updating to iOS 16.7.8/17.5+, iPadOS 16.7.8/17.5+, macOS 12.7.5/13.6.7/14.5, tvOS 17.5, or visionOS 1.2 as appropriate for each affected device.
iOS 16.7.8+/iOS 17.5+, iPadOS 16.7.8+/iPadOS 17.5+, macOS 12.7.5+/13.6.7+/14.5+, tvOS 17.5+, visionOS 1.2+
- Identify the currently installed OS version on the affected device (iPhone, iPad, Mac, Apple TV, or Apple Vision Pro)
- Determine which product category and version range the device falls into from the affected versions list
- For iOS/iPadOS 16.x devices: upgrade to iOS/iPadOS 16.7.8 or later
- For iOS/iPadOS 17.0-17.4 devices: upgrade to iOS/iPadOS 17.5 or later
- For macOS Monterey (12.x) devices: upgrade to macOS 12.7.5 or later
- For macOS Ventura (13.x) devices: upgrade to macOS 13.6.7 or later
- For macOS Sonoma (14.x) devices: upgrade to macOS 14.5 or later
- For tvOS 17.x devices: upgrade to tvOS 17.5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27817 — 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
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- seclists.org
- 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-27817 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