CVE-2024-27863
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 · uneditedAn information disclosure issue was addressed with improved private data redaction for log entries. This issue is fixed in iOS 17.6 and iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6. A local attacker may be able to determine kernel memory layout.
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 confidenceA local information disclosure vulnerability in Apple's log redaction mechanism allowed unredacted kernel memory layout information to be written to log entries. A local attacker with code execution or log access could potentially use this kernel memory layout information to defeat ASLR protections in kernel exploits.
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.6< 17.6< 14.6< 17.6< 1.3< 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 versionGo to Settings > General > About > Software Version on the deviceAffected if The version is earlier than 17.6
-
Check macOS versionClick the Apple menu and select About This MacAffected if The version is earlier than 14.6 (Sonoma)
-
Check tvOS versionGo to Settings > General > About > Version on the Apple TVAffected if The version is earlier than 17.6
-
Check watchOS versionOpen the Watch app on paired iPhone, go to General > AboutAffected if The version is earlier than 10.6
-
Check visionOS versionGo to Settings > General > About on the Vision Pro deviceAffected if The version is earlier than 1.3
-
Inspect system logs for unredacted kernel addressesReview system log files (such as via Console app on macOS or logd on iOS) for entries that may contain kernel memory addresses or memory layout information that should have been redactedAffected if Logs contain readable kernel memory addresses or heap/layout metadata that appears unredacted
The environment is affected if the installed Apple OS version is below the patched release (17.6 for iOS/iPadOS/tvOS, 14.6 for macOS, 1.3 for visionOS, 10.6 for watchOS) AND system logs contain unredacted kernel memory layout information.
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.310.614.6
Apply the vendor-supplied patches for the affected Apple operating systems (iOS 17.6+, iPadOS 17.6+, macOS Sonoma 14.6+, tvOS 17.6+, visionOS 1.3+, watchOS 10.6+).
iOS 17.6 / iPadOS 17.6 / macOS Sonoma 14.6 / tvOS 17.6 / visionOS 1.3 / watchOS 10.6
- Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
- Check the current installed OS version in Settings > General > About (iOS/iPadOS/watchOS/visionOS) or System Settings > General > About (macOS)
- Back up the device data using iCloud or Finder/iTunes as a precaution
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 17.6/iPadOS 17.6
- For Mac: Go to System Settings > General > Software Update and install macOS Sonoma 14.6
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.6
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 1.3
- For Apple Watch: On the iPhone, open the Watch app, go to My Watch > General > Software Update and install watchOS 10.6
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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-27863 — 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
- 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
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-27863 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