CVE-2024-54486
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 · uneditedThe 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 font may result in the 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 · moderate confidenceThis is a memory disclosure vulnerability in Apple operating systems where processing a maliciously crafted font file leads to exposure of process memory. The vulnerability was in font parsing/processing code, and Apple addressed it with improved validation checks during font processing.
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< 17.7.3>= 18.0, < 18.2< 18.2< 13.7.2>= 14.0, < 14.7.2>= 15.0, < 15.2< 18.2< 2.2< 11.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Apple productDetermine which Apple operating system is running (iOS, iPadOS, macOS, tvOS, visionOS, or watchOS)Affected if The product is any of these six Apple OS types
-
Check the installed iOS or iPadOS versionGo to Settings > General > About on iPhone or iPad, or use the command: sw_vers (iOS) or system_profiler SPSoftwareDataType (iPadOS)Affected if The version is less than 18.2, or is 18.0 or 18.1 (iOS), or is less than 17.7.3, or is 18.0 or 18.1 (iPadOS)
-
Check the installed macOS versionGo to System Settings > General > About, or run sw_vers in TerminalAffected if The version is less than 13.7.2 (Ventura), or is 14.0-14.7.1 (Sonoma), or is 15.0-15.1 (Sequoia)
-
Check the installed tvOS, visionOS, or watchOS versionOn Apple TV go to Settings > General > About > Version; on Vision Pro go to Settings > General > About; on Apple Watch go to Settings > General > AboutAffected if tvOS is less than 18.2, visionOS is less than 2.2, or watchOS is less than 11.2
-
Confirm font processing exposureThe vulnerability is triggered when processing font files. Determine if the system has been used to open or process font files from untrusted sources, though font processing is a built-in system featureAffected if The system processes font files as a standard function, and the version is in the affected range
The environment is affected if the Apple operating system version falls within any of the vulnerable version ranges listed for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS.
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 · scoped2.211.213.7.2
Update to the fixed versions: iOS 18.2, iPadOS 17.7.3/18.2, macOS Ventura 13.7.2/Sonoma 14.7.2/Sequoia 15.2, tvOS 18.2, visionOS 2.2, or watchOS 11.2. Avoid opening font files from untrusted sources until patching is complete.
iOS 18.2 / iPadOS 18.2 / iPadOS 17.7.3 / macOS Ventura 13.7.2 / macOS Sonoma 14.7.2 / macOS Sequoia 15.2 / tvOS 18.2 / visionOS 2.2 / watchOS 11.2
- Identify the Apple device type (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
- Back up the device before updating
- For iPhone: Go to Settings > General > Software Update and upgrade to iOS 18.2 or later
- For iPad: Go to Settings > General > Software Update and upgrade to iPadOS 18.2 or later (or iPadOS 17.7.3 if staying on iOS 17)
- For Mac: Go to System Settings > General > Software Update and upgrade to macOS Ventura 13.7.2, Sonoma 14.7.2, or Sequoia 15.2 as appropriate
- For Apple TV: Go to Settings > General > Software Update and upgrade to tvOS 18.2
- For Apple Vision Pro: Go to Settings > General > Software Update and upgrade to visionOS 2.2
- For Apple Watch: Go to Settings > General > Software Update on the iPhone companion app and upgrade to watchOS 11.2
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-54486 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54486 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