dbcve.org
IpadosOperating system · Apple

CVE-2024-44240

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 specially crafted font file processed by vulnerable Apple operating systems can cause the application handling the font to leak portions of its memory contents to an attacker. This information disclosure occurs due to insufficient validation checks when parsing font data.

MitigationApply the vendor-provided patches for all affected Apple products (iOS 17.7.1+, iPadOS 17.7.1+, macOS 13.7.1+, tvOS 18.1+, visionOS 2.1+, watchOS 11.1+). No public workarounds are available.

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, < 18.1
Iphone OsOperating system
Affected:< 17.7.1>= 18.0, < 18.1
macOSOperating system
Affected:>= 13.0, < 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. Check iOS or iPadOS version on iPhone or iPad
    Go to Settings > General > About and note the Version number
    Affected if Version is earlier than 17.7.1, OR falls between 18.0 and 18.0.x (where x is less than 1)
  2. Check macOS version on Mac computer
    Go to System Settings > About (or Apple menu > About This Mac) and note the macOS version
    Affected if Version is 13.0 through 13.7.0, OR 14.0 through 14.7.0
  3. Check tvOS version on Apple TV
    Go to Settings > General > About > Version
    Affected if Version is earlier than 18.1
  4. Check visionOS version on Apple Vision Pro
    Go to Settings > General > About and note the version
    Affected if Version is earlier than 2.1
  5. Check watchOS version on Apple Watch
    Open the Watch app on iPhone, go to My Watch > General > About and note the watchOS version
    Affected if Version is earlier than 11.1

The device is affected if it runs any unpatched Apple operating system version within the ranges listed above; the font parsing vulnerability is present in the core OS and triggers when processing a malicious font file.

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-provided patches for all affected Apple products (iOS 17.7.1+, iPadOS 17.7.1+, macOS 13.7.1+, tvOS 18.1+, visionOS 2.1+, watchOS 11.1+). No public workarounds are available.

Recommended fix High confidence

iOS 17.7.1 or iOS 18.1; iPadOS 17.7.1 or iPadOS 18.1; macOS Ventura 13.7.1, macOS Sonoma 14.7.1, or macOS Sequoia 15.1; tvOS 18.1; visionOS 2.1; watchOS 11.1

  1. Identify the Apple device type (iPhone, iPad, Mac, Apple TV, Apple Watch, or Apple Vision Pro)
  2. Check the current OS version on the device
  3. For iPhone/iPad: upgrade to iOS/iPadOS 17.7.1 (if staying on 17.x) or iOS/iPadOS 18.1 (if moving to 18.x)
  4. For Mac: upgrade to macOS Ventura 13.7.1, macOS Sonoma 14.7.1, or macOS Sequoia 15.1 depending on the current major version
  5. For Apple TV: upgrade to tvOS 18.1
  6. For Apple Watch: upgrade to watchOS 11.1
  7. For Apple Vision Pro: upgrade to visionOS 2.1
  8. Install the update via Settings > General > Software Update (iOS/iPadOS/watchOS/tvOS/visionOS) or System Settings > Software Update (macOS)
Caveat Standard OS update - ensure backups exist before updating; some older 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
  • Testing1.0 h
  • Review / QA1.0 h
4.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-44240 — 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-44240 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