dbcve.org
IpadosOperating system · Apple

CVE-2024-54517

HIGH · 7.8 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 11.2 / 15.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
The issue was addressed with improved bounds checks. This issue is fixed in iOS 18.2 and iPadOS 18.2, macOS Sequoia 15.2, tvOS 18.2, watchOS 11.2. An app may be able to corrupt coprocessor memory.

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 confidence

A bounds checking vulnerability in Apple operating systems allows a malicious local application to corrupt coprocessor memory. The flaw involves insufficient validation of memory access bounds, potentially enabling privilege escalation or unexpected behavior through coprocessor memory manipulation.

MitigationApply the vendor-supplied updates: iOS 18.2 and iPadOS 18.2, macOS Sequoia 15.2, tvOS 18.2, or watchOS 11.2 and later. Prioritize devices with sensitive coprocessor functions (Secure Enclave, T2 chip, or similar).

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
IpadosOperating system
Affected:< 18.2
Iphone OsOperating system
Affected:< 18.2
macOSOperating system
Affected:< 15.2
TvosOperating system
Affected:< 18.2
WatchosOperating system
Affected:< 11.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Apple device and operating system
    On iOS/iPadOS: go to Settings > General > About to see the version. On macOS: click Apple menu > About This Mac. On tvOS/watchOS: go to Settings > General > About.
    Affected if The installed version is iOS, iPadOS, tvOS, or watchOS earlier than 18.2, or macOS earlier than 15.2
  2. Verify the exact version number
    Compare your displayed version number against the affected ranges: iOS < 18.2, iPadOS < 18.2, macOS < 15.2, tvOS < 18.2, watchOS < 11.2.
    Affected if Your version falls below these thresholds in any affected product category
  3. Determine if your device includes a coprocessor
    Check your device specifications for the presence of a Secure Enclave processor (iPhones 5s and later, iPads with A7 chip or later), T2 Security Chip (certain Macs), or similar coprocessor.
    Affected if Your device has a coprocessor like Secure Enclave or T2 AND your OS version is vulnerable per step 2
  4. Check for locally installed third-party applications
    Review your installed applications. The vulnerability requires a malicious local application to already be installed to exploit the bounds checking flaw.
    Affected if You have applications installed from outside the official App Store (sideloaded) or have granted extensive permissions to third-party apps, combined with a vulnerable OS version

You are affected if your Apple device runs an OS version below 18.2 for iOS/iPadOS/tvOS/watchOS or below 15.2 for macOS, and your device contains a coprocessor like the Secure Enclave or T2 chip.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.2 / 15.2 / 18.2 or later
Fixed in 11.215.218.2
Interim mitigation

Apply the vendor-supplied updates: iOS 18.2 and iPadOS 18.2, macOS Sequoia 15.2, tvOS 18.2, or watchOS 11.2 and later. Prioritize devices with sensitive coprocessor functions (Secure Enclave, T2 chip, or similar).

Recommended fix High confidence

iOS 18.2, iPadOS 18.2, macOS Sequoia 15.2, tvOS 18.2, watchOS 11.2

  1. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 18.2 or iPadOS 18.2, or connect device to computer and update via Finder/iTunes
  2. For Mac: Go to System Settings > General > Software Update and install macOS Sequoia 15.2, or use Software Update in App Store
  3. For Apple TV: Go to Settings > General > Software Update and install tvOS 18.2
  4. For Apple Watch: On iPhone, open Watch app, go to My Watch > General > Software Update and install watchOS 11.2, or go to Settings > General > Software Update on Apple Watch directly
Caveat OS updates may include new system requirements or affect compatibility with older apps; backup data before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-54517 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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