CVE-2024-23296
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 memory corruption issue was addressed with improved validation. This issue is fixed in iOS 16.7.8 and iPadOS 16.7.8, iOS 17.4 and iPadOS 17.4, macOS Monterey 12.7.6, macOS Sonoma 14.4, macOS Ventura 13.6.7, tvOS 17.4, visionOS 1.1, watchOS 10.4. An attacker with arbitrary kernel read and write capability may be able to bypass kernel memory protections. Apple is aware of a report that this issue may have been exploited.
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 confidenceMemory corruption vulnerability in Apple kernel allows attackers with existing arbitrary kernel read/write capabilities to bypass kernel memory protections. The issue was addressed through improved memory validation. This is a defense-in-depth bypass that requires the attacker to already have kernel-level access.
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.4< 16.7.8>= 17.0, < 17.4>= 12.0, < 12.7.6>= 13.0, < 13.6.7>= 14.0, < 14.4< 17.4< 1.1< 10.4CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 version on iPhoneGo to Settings > General > About on the device and note the 'Version' field (e.g., 17.3). Alternatively, run 'sw_vers' via SSH or MDM.Affected if Version is less than 16.7.8, OR version is 17.0 through 17.3.x (anything >= 17.0 but < 17.4)
-
Check iPadOS version on iPadGo to Settings > General > About on the device and note the 'Version' field. Alternatively, run 'sw_vers' via SSH or MDM.Affected if Version is less than 16.7.8, OR version is 17.0 through 17.3.x (anything >= 17.0 but < 17.4)
-
Check macOS versionRun 'sw_vers -productVersion' in Terminal, or go to System Settings > About > macOS version.Affected if Version is 12.0 through 12.7.5, OR 13.0 through 13.6.6, OR 14.0 through 14.3.x (anything >= 14.0 but < 14.4)
-
Check tvOS versionRun 'sw_vers -productVersion' via SSH if available, or check via Apple TV Settings > General > About.Affected if Version is less than 17.4 (any version before 17.4)
-
Check visionOS versionCheck via Vision Pro Settings > General > About.Affected if Version is less than 1.1 (any version before 1.1)
-
Check watchOS versionOpen the Watch app on paired iPhone, go to My Watch > General > About, or check on Apple Watch via Settings > General > About.Affected if Version is less than 10.4 (any version before 10.4)
A device is affected if its operating system version falls within any of the vulnerable ranges listed for that product: the device must be running an unpatched version of iOS, iPadOS, macOS, tvOS, visionOS, or watchOS.
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.110.412.7.6
Apply vendor-supplied security updates to all affected Apple devices: iOS 16.7.8/17.4, iPadOS 16.7.8/17.4, macOS 12.7.6/13.6.7/14.4, tvOS 17.4, visionOS 1.1, and watchOS 10.4.
Upgrade to iOS/iPadOS 16.7.8 or 17.4, macOS 12.7.6/13.6.7/14.4, tvOS 17.4, visionOS 1.1, or watchOS 10.4 as applicable to your device
- Back up your device data before updating
- Determine your current device and OS version via Settings > General > About (iOS/iPadOS), System Settings or About This Mac (macOS), or Settings > General > About (tvOS, watchOS, visionOS)
- For iPhone/iPad: Update to iOS/iPadOS 16.7.8 or iOS/iPadOS 17.4 via Settings > General > Software Update
- For Mac: Update to macOS Monterey 12.7.6, macOS Ventura 13.6.7, or macOS Sonoma 14.4 via System Settings > General > Software Update
- For Apple TV: Update to tvOS 17.4 via Settings > General > Apple TV Software Updates
- For Apple Watch: Update to watchOS 10.4 via the Watch app on iPhone > General > Software Update
- For Apple Vision Pro: Update to visionOS 1.1 via Settings > General > Software Update
- After update, verify the new version is installed
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-23296 — 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
- support.apple.com
- support.apple.com
- support.apple.com
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- www.cisa.gov
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23296 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