dbcve.org
IpadosOperating system · Apple

CVE-2024-54501

MEDIUM · 5.5 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 2.2 / 11.2 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
The issue was addressed with improved checks. This issue is fixed in iOS 18.2 and iPadOS 18.2, iPadOS 17.7.3, macOS Sequoia 15.2, macOS Sonoma 14.7.2, macOS Ventura 13.7.2, tvOS 18.2, visionOS 2.2, watchOS 11.2. Processing a maliciously crafted file may lead to a denial of service.

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 · moderate confidence

A denial of service vulnerability in multiple Apple operating systems allows remote attackers to cause a system crash or service disruption by tricking users into processing a maliciously crafted file. The fix involves implementing improved input validation checks during file parsing operations.

MitigationApply the available vendor patches for the affected Apple operating systems. For third-party applications handling file input, implement robust input validation and bounds checking before processing any file data.

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:< 17.7.3>= 18.0, < 18.2
Iphone OsOperating system
Affected:< 18.2
macOSOperating system
Affected:< 13.7.2>= 14.0, < 14.7.2>= 15.0, < 15.2
TvosOperating system
Affected:< 18.2
VisionosOperating system
Affected:< 2.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Check iOS version
    Go to Settings > General > About on iPhone, or Settings > General > About on iPad. Note the version number.
    Affected if The version is less than 18.2, or is 17.x and less than 17.7.3
  2. Check macOS version
    Click Apple menu > About This Mac. Note the version number.
    Affected if The version is less than 13.7.2, or is 14.x and less than 14.7.2, or is 15.x and less than 15.2
  3. Check tvOS version
    Go to Settings > General > About > Version on Apple TV.
    Affected if The version is less than 18.2
  4. Check watchOS version
    Open the Watch app on iPhone, go to My Watch > General > About. Note the version.
    Affected if The version is less than 11.2
  5. Check visionOS version
    Go to Settings > General > About on Apple Vision Pro.
    Affected if The version is less than 2.2
  6. Audit third-party file processing applications
    Review any installed third-party applications that handle file input. Check their documentation or settings for input validation or file parsing configurations.
    Affected if Applications lack input validation for file parsing and process untrusted files

You are affected if your Apple device runs an OS version that falls within any of the vulnerable ranges listed for your device type.

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 2.2 / 11.2 / 13.7.2 or later
Fixed in 2.211.213.7.2
Interim mitigation

Apply the available vendor patches for the affected Apple operating systems. For third-party applications handling file input, implement robust input validation and bounds checking before processing any file data.

Recommended fix High confidence

iOS 18.2 / iPadOS 17.7.3 or 18.2 / macOS 13.7.2, 14.7.2, or 15.2 / tvOS 18.2 / visionOS 2.2 / watchOS 11.2 (depending on device and current version)

  1. Identify the device type (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
  2. Identify the current OS version from Settings > General > About (iOS/iPadOS/tvOS/visionOS/watchOS) or System Settings > General > About This Mac (macOS
  3. For iPadOS: If on version 17.x, upgrade to 17.7.3; if on version 18.x, upgrade to 18.2
  4. For iPhone: Upgrade to iOS 18.2
  5. For macOS Ventura (13.x): Upgrade to 13.7.2; for macOS Sonoma (14.x): Upgrade to 14.7.2; for macOS Sequoia (15.x): Upgrade to 15.2
  6. For Apple TV: Upgrade to tvOS 18.2
  7. For Apple Vision Pro: Upgrade to visionOS 2.2
  8. For Apple Watch: Upgrade to watchOS 11.2
Caveat Standard Apple OS update risks: ensure backup before upgrading; some legacy apps may become incompatible with newer OS versions

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,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 $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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