dbcve.org
IpadosOperating system · Apple

CVE-2024-44201

MEDIUM · 5.5 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 13.7.2 / 14.7.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 memory handling. This issue is fixed in iOS 18.1 and iPadOS 18.1, iPadOS 17.7.3, macOS Sequoia 15.1, macOS Sonoma 14.7.2, macOS Ventura 13.7.2. Processing a malicious 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 memory handling vulnerability in Apple's iOS, iPadOS, and macOS allows denial-of-service when processing a maliciously crafted file. The vulnerability stems from improper memory management during file parsing operations, which can be triggered by a specially designed file causing a crash or system unresponsiveness.

MitigationApply the vendor-supplied security updates: iOS 18.1, iPadOS 18.1/17.7.3, macOS Sequoia 15.1, macOS Sonoma 14.7.2, or macOS Ventura 13.7.2. Avoid opening files from untrusted sources.

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.1
Iphone OsOperating system
Affected:< 18.1
macOSOperating system
Affected:>= 13.0, < 13.7.2>= 14.0, < 14.7.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 on iPhone
    Go to Settings > General > About > Version on the device
    Affected if Version is earlier than 18.1 (the version shown will be like 18.0.x or earlier)
  2. Check iPadOS version on iPad
    Go to Settings > General > About > Version on the device
    Affected if Version is earlier than 17.7.3, or is 18.0.x (meaning version is < 18.1)
  3. Check macOS version
    Click the Apple menu > About This Mac and note the version number under the name
    Affected if Version is 13.0 through 13.7.1, or 14.0 through 14.7.1 (the build shows a version like 13.x.x or 14.x.x)
  4. Identify file parsing usage
    Determine if the device or Mac regularly opens files from external or untrusted sources (email attachments, downloaded files, third-party apps that import documents)
    Affected if The user processes files from untrusted sources using built-in apps (Photos, Files, Safari, Mail, Preview, or other native file-handling applications)

A user is affected if their OS version falls within the vulnerable ranges AND they open files from untrusted or unknown sources using native parsing features.

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 13.7.2 / 14.7.2 / 17.7.3 or later
Fixed in 13.7.214.7.217.7.3
Interim mitigation

Apply the vendor-supplied security updates: iOS 18.1, iPadOS 18.1/17.7.3, macOS Sequoia 15.1, macOS Sonoma 14.7.2, or macOS Ventura 13.7.2. Avoid opening files from untrusted sources.

Recommended fix High confidence

iOS 18.1, iPadOS 18.1, iPadOS 17.7.3, macOS Sequoia 15.1, macOS Sonoma 14.7.2, or macOS Ventura 13.7.2 (depending on device)

  1. Identify the current installed iOS/iPadOS/macOS version on the affected device
  2. For iPhone/iPad: Go to Settings > General > Software Update and install the latest available update
  3. For macOS: Open System Settings > General > Software Update and install available updates
  4. Alternatively, manually download and install iOS 18.1, iPadOS 18.1, iPadOS 17.7.3, macOS Sequoia 15.1, macOS Sonoma 14.7.2, or macOS Ventura 13.7.2 from Apple
  5. After upgrade, verify the system is running a version >= the fixed releases listed
Caveat Standard Apple upgrade considerations: ensure app compatibility and backup data before updating

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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