dbcve.org
IpadosOperating system · Apple

CVE-2024-44302

MEDIUM · 5.5 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 2.1 / 11.1 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 17.7.1 and iPadOS 17.7.1, iOS 18.1 and iPadOS 18.1, macOS Sequoia 15.1, macOS Sonoma 14.7.1, macOS Ventura 13.7.1, tvOS 18.1, visionOS 2.1, watchOS 11.1. 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 · high confidence

A memory disclosure vulnerability in Apple's font processing subsystem allows a maliciously crafted font file to leak process memory contents. The vulnerability stems from insufficient input validation when parsing font data, which could expose sensitive information from the application's memory space.

MitigationApply the vendor-supplied OS updates (iOS 17.7.1+, iPadOS 17.7.1+, macOS 13.7.1+, tvOS 18.1+, visionOS 2.1+, watchOS 11.1+) to all affected devices. Avoid processing untrusted font files until patches are applied.

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.1= 18.0
Iphone OsOperating system
Affected:< 17.7.1= 18.0
macOSOperating system
Affected:< 13.7.1>= 14.0, < 14.7.1
TvosOperating system
Affected:< 18.1
VisionosOperating system
Affected:< 2.1
WatchosOperating system
Affected:< 11.1

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Identify your Apple device OS and exact version
    On macOS, run 'sw_vers -productVersion'. On iOS/iPadOS, go to Settings > General > About. On tvOS/watchOS/visionOS, go to Settings > General > About > Version
    Affected if Unable to determine the OS version
  2. Check if iOS or iPadOS is affected
    If running iOS or iPadOS, compare your version to the affected ranges: any version < 17.7.1, or exactly version 18.0
    Affected if Your iOS/iPadOS version is 17.7.0 or earlier, or is exactly 18.0
  3. Check if macOS is affected
    If running macOS, run 'sw_vers -productVersion' and compare to affected ranges: any version < 13.7.1, or version 14.0 through 14.7.0
    Affected if Your macOS version is 13.7.0 or earlier, or between 14.0 and 14.7.0 inclusive
  4. Check if tvOS, watchOS, or visionOS is affected
    If running tvOS (check version < 18.1), watchOS (check version < 11.1), or visionOS (check version < 2.1), note that all versions prior to these thresholds are affected
    Affected if Your tvOS version is 18.0 or earlier, watchOS is 11.0 or earlier, or visionOS is 2.0 or earlier

If your Apple device OS version falls within any of the specified vulnerable ranges, the font processing subsystem is affected by this memory disclosure vulnerability.

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.1 / 11.1 / 13.7.1 or later
Fixed in 2.111.113.7.1
Interim mitigation

Apply the vendor-supplied OS updates (iOS 17.7.1+, iPadOS 17.7.1+, macOS 13.7.1+, tvOS 18.1+, visionOS 2.1+, watchOS 11.1+) to all affected devices. Avoid processing untrusted font files until patches are applied.

Recommended fix High confidence

Upgrade to iOS 17.7.1/iPadOS 17.7.1, iOS 18.1/iPadOS 18.1, macOS Ventura 13.7.1/macOS Sonoma 14.7.1/macOS Sequoia 15.1, tvOS 18.1, visionOS 2.1, or watchOS 11.1 as appropriate for your device

  1. Back up your device data before performing any OS update
  2. For iPhone/iPad: Go to Settings > General > Software Update and install the available update (iOS 17.7.1 or iOS 18.1, iPadOS 17.7.1 or iPadOS 18.1)
  3. For Mac: Go to System Settings > General > Software Update and install the available update (macOS Ventura 13.7.1, macOS Sonoma 14.7.1, or macOS Sequoia 15.1)
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 18.1
  5. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2.1
  6. For Apple Watch: Go to Settings > General > Software Update on the iPhone paired with the watch and install watchOS 11.1
  7. After updating, verify the installed version matches one of the fixed releases

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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