dbcve.org
IpadosOperating system · Apple

CVE-2024-54500

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 →
57/100
Remediation priority · Elevated
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 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 image may result in disclosure of process 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 memory disclosure vulnerability exists in Apple's image processing components across multiple operating systems. When processing a maliciously crafted image, insufficient validation checks allow inadvertent leakage of process memory contents to an attacker.

MitigationApply the available Apple security updates (iOS 18.2, iPadOS 17.7.3/18.2, macOS 13.7.2/14.7.2/15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2) to all affected devices.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
    Go to Settings > General > About and note the version number (e.g., 18.1, 17.7)
    Affected if Version is less than 18.2 (all iOS versions before 18.2 are affected)
  2. Check iPadOS version on iPad
    Go to Settings > General > About and note the version number
    Affected if Version is less than 17.7.3 OR is 18.0, 18.1 (less than 18.2)
  3. Check macOS version
    Open About This Mac (Apple menu > About This Mac) or run 'sw_vers' in Terminal
    Affected if Version is 13.x before 13.7.2, 14.x before 14.7.2, or 15.x before 15.2
  4. Check tvOS version
    Go to Settings > General > About on Apple TV
    Affected if Version is less than 18.2
  5. Check watchOS version
    Open the Watch app on paired iPhone, go to General > About, or on Apple Watch go to Settings > General > About
    Affected if Version is less than 11.2
  6. Check visionOS version
    Go to Settings > General > About on Apple Vision Pro
    Affected if Version is less than 2.2

If the device runs any affected OS version listed above, processing untrusted images could leak memory contents to an attacker.

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 Apple security updates (iOS 18.2, iPadOS 17.7.3/18.2, macOS 13.7.2/14.7.2/15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2) to all affected devices.

Recommended fix High confidence

iOS 18.2 / iPadOS 17.7.3 / iPadOS 18.2 / macOS Ventura 13.7.2 / macOS Sonoma 14.7.2 / macOS Sequoia 15.2 / tvOS 18.2 / visionOS 2.2 / watchOS 11.2 (depending on device)

  1. Identify the current version of the affected Apple device (iPadOS, iOS, macOS, tvOS, visionOS, or watchOS)
  2. For iPhone users: Upgrade to iOS 18.2 or later
  3. For iPad users: Upgrade to iPadOS 17.7.3 or iPadOS 18.2 or later
  4. For Mac users: Upgrade to macOS Ventura 13.7.2, macOS Sonoma 14.7.2, or macOS Sequoia 15.2 or later
  5. For Apple TV users: Upgrade to tvOS 18.2 or later
  6. For Apple Vision Pro users: Upgrade to visionOS 2.2 or later
  7. For Apple Watch users: Upgrade to watchOS 11.2 or later
  8. After upgrade, verify the new version in Settings > General > About (iOS/iPadOS) or System Settings > About (macOS)
Caveat Standard upgrade considerations apply - review Apple's release notes for any feature changes before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA2.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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