IpadosOperating system · Apple

CVE-2024-54560

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-10
Fix available
A fix is available. Upgrade to 11.0 / 15.0 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
A logic issue was addressed with improved checks. This issue is fixed in iOS 18 and iPadOS 18, macOS Sequoia 15, tvOS 18, watchOS 11. A malicious app may be able to modify other apps without having App Management permission.

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

This is a logic flaw in Apple's mobile and desktop operating systems that allows a malicious application to modify other applications without possessing the required App Management permission. The vulnerability represents a privilege escalation issue where apps can bypass permission checks meant to protect against unauthorized app modification.

MitigationUpdate affected devices to iOS 18, iPadOS 18, macOS Sequoia 15, tvOS 18, or watchOS 11 or later to receive the vendor patch.

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.0
Iphone OsOperating system
Affected:< 18.0
macOSOperating system
Affected:< 15.0
TvosOperating system
Affected:< 18.0
WatchosOperating system
Affected:< 11.0

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checks

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

  1. Check iOS version on iPhone
    On the device, go to Settings > General > About and read the Software Version field, or connect to a computer with iTunes/Finder and check the device summary
    Affected if The version is earlier than 18.0
  2. Check iPadOS version on iPad
    On the device, go to Settings > General > About and read the Software Version field
    Affected if The version is earlier than 18.0
  3. Check macOS version on Mac
    Click the Apple menu and select About This Mac, or run the command 'sw_vers' in Terminal
    Affected if The version number displayed is earlier than 15.0
  4. Check tvOS version on Apple TV
    Go to Settings > General > About on the Apple TV and read the version field
    Affected if The version is earlier than 18.0
  5. Check watchOS version on Apple Watch
    On the watch, go to Settings > General > About, or open the Watch app on a paired iPhone and check the watch's About section
    Affected if The version is earlier than 11.0

The device is affected if it runs any version below the respective threshold: iOS/iPadOS/tvOS below 18.0, macOS below 15.0, or watchOS below 11.0.

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.0 / 15.0 / 18.0 or later
Fixed in 11.015.018.0
Interim mitigation

Update affected devices to iOS 18, iPadOS 18, macOS Sequoia 15, tvOS 18, or watchOS 11 or later to receive the vendor patch.

Recommended fix High confidence

iOS 18 and iPadOS 18, macOS Sequoia 15, tvOS 18, watchOS 11

  1. Check the current OS version on the device (Settings > General > About on iOS/iPadOS, System Settings > About on macOS, Settings > General > About on tvOS, Settings > General on watchOS)
  2. Back up important data using iCloud or local backup before updating
  3. Install the latest available update: iOS 18 or iPadOS 18 for iPhone/iPad devices, macOS Sequoia 15 for Mac computers, tvOS 18 for Apple TV, or watchOS 11 for Apple Watch
  4. After updating, verify the version installed matches or exceeds the fixed release
Caveat Major OS upgrades may cause incompatibility with older applications; review app compatibility 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
1.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54560 — 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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-54560 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