CVE-2024-23286
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 buffer overflow issue was addressed with improved memory handling. This issue is fixed in iOS 16.7.6 and iPadOS 16.7.6, iOS 17.4 and iPadOS 17.4, macOS Monterey 12.7.4, macOS Sonoma 14.4, macOS Ventura 13.6.5, tvOS 17.4, visionOS 1.1, watchOS 10.4. Processing an image may lead to arbitrary code execution.
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 buffer overflow vulnerability exists in Apple's image processing components across iOS, iPadOS, macOS, tvOS, visionOS, and watchOS. The vulnerability stems from improper memory handling when processing maliciously crafted images, allowing an attacker to achieve arbitrary code execution with kernel-level privileges.
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.6>= 17.0, < 17.4< 16.7.6>= 17.0, < 17.4>= 12.0, < 12.7.4>= 13.0, < 13.6.5>= 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
- 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 version on iPhoneGo to Settings > General > About > Version, or run 'sw_vers' via SSH/terminal if availableAffected if Version is earlier than 16.7.6, or falls between 17.0 and 17.4 (excluding 17.4)
-
Check iPadOS version on iPadGo to Settings > General > About > Version, or run 'sw_vers' via SSH/terminal if availableAffected if Version is earlier than 16.7.6, or falls between 17.0 and 17.4 (excluding 17.4)
-
Check macOS versionClick Apple menu > About This Mac > Version, or run 'sw_vers' in TerminalAffected if Version is 12.0-12.7.3, 13.0-13.6.4, or 14.0-14.3 (any version before the fixed releases 12.7.4, 13.6.5, or 14.4)
-
Check tvOS versionGo to Settings > General > About > Version on Apple TV, or check via Xcode/device management toolsAffected if Version is earlier than 17.4
-
Check visionOS versionGo to Settings > About > Version on Apple Vision Pro, or check via device management toolsAffected if Version is earlier than 1.1
-
Check watchOS versionOpen the Watch app on paired iPhone > General > About, or go to Settings > General > About on Apple WatchAffected if Version is earlier than 10.4
The device is affected if its operating system version falls within any of the unpatched ranges listed for that product; update to the fixed version to resolve.
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.4
Apply the vendor-supplied security updates for the respective operating systems (iOS 16.7.6/17.4, iPadOS 16.7.6/17.4, macOS 12.7.4/13.6.5/14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4) to all affected devices. Prioritize endpoint devices given the CVSS 7.8 score indicating high exploitability potential.
Upgrade to iOS 16.7.6/iPadOS 16.7.6 or iOS 17.4/iPadOS 17.4; macOS 12.7.4/13.6.5/14.4; tvOS 17.4; visionOS 1.1; watchOS 10.4
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 16.7.6 or iOS 17.4 (depending on your device compatibility)
- For Mac: Go to System Settings > General > Software Update and install the appropriate update: macOS Monterey 12.7.4, macOS Ventura 13.6.5, or macOS Sonoma 14.4
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.4
- For Apple Watch: Open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 10.4
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 1.1
- After updating, verify the fix by checking Settings > General > About for the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23286 — 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
- 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
- support.apple.com
- support.apple.com
- support.apple.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23286 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