dbcve.org
IpadosOperating system · Apple

CVE-2024-44285

HIGH · 7.8 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 2.1 / 11.1 or later.
See remediation →
80/100
Remediation priority · High
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
A use-after-free issue was addressed with improved memory management. This issue is fixed in iOS 18.1 and iPadOS 18.1, macOS Sequoia 15.1, tvOS 18.1, visionOS 2.1, watchOS 11.1. An app may be able to cause unexpected system termination or corrupt kernel 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 confidence

A use-after-free vulnerability in Apple's kernel allows a malicious local application to cause unexpected system termination or corrupt kernel memory. The vulnerability results from improper memory management that can be exploited by an app to gain elevated privileges or cause denial-of-service conditions.

MitigationDeploy the vendor-supplied security updates (iOS 18.1, iPadOS 18.1, macOS Sequoia 15.1, tvOS 18.1, visionOS 2.1, or watchOS 11.1) to all affected Apple devices to remediate the vulnerability.

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:>= 18.0, < 18.1
Iphone OsOperating system
Affected:>= 18.0, < 18.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 on the iPhone and locate the 'Version' field. Confirm if the version is 18.0 (the only affected version in the range).
    Affected if Version shows 18.0 exactly, as iOS 18.1 and later are patched.
  2. Check iPadOS version on iPad
    Go to Settings > General > About on the iPad and locate the 'Version' field. Confirm if the version is 18.0.
    Affected if Version shows 18.0 exactly, as iPadOS 18.1 and later are patched.
  3. Check tvOS version on Apple TV
    On Apple TV, go to Settings > General > About > Version to view the tvOS build version.
    Affected if Version is earlier than 18.1, as any version below 18.1 is affected.
  4. Check visionOS version on Apple Vision
    On Apple Vision, go to Settings > General > About to view the visionOS version number.
    Affected if Version is earlier than 2.1, as any version below 2.1 is affected.
  5. Check watchOS version on Apple Watch
    On Apple Watch, open the Watch app on paired iPhone, go to My Watch > General > About, or on the watch go to Settings > General > About.
    Affected if Version is earlier than 11.1, as any version below 11.1 is affected.
  6. Identify devices via MDM or inventory
    If using an enterprise MDM solution, query device inventory reports to list all enrolled iOS, iPadOS, tvOS, visionOS, and watchOS devices with their OS versions.
    Affected if Any managed device reports OS version in the affected ranges (iOS/iPadOS 18.0, tvOS below 18.1, visionOS below 2.1, watchOS below 11.1).

A device is affected if it runs any iOS or iPadOS version 18.0, any tvOS version below 18.1, any visionOS version below 2.1, or any watchOS version below 11.1.

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 / 18.1 or later
Fixed in 2.111.118.1
Interim mitigation

Deploy the vendor-supplied security updates (iOS 18.1, iPadOS 18.1, macOS Sequoia 15.1, tvOS 18.1, visionOS 2.1, or watchOS 11.1) to all affected Apple devices to remediate the vulnerability.

Recommended fix High confidence

iOS 18.1/iPadOS 18.1, tvOS 18.1, visionOS 2.1, or watchOS 11.1 (or later respective versions)

  1. 1. Identify the device type (iPhone, iPad, Apple TV, Apple Vision Pro, or Apple Watch)
  2. 2. Check the current installed OS version on the device
  3. 3. For iPhone or iPad: Upgrade to iOS 18.1 or iPadOS 18.1 or later
  4. 4. For Apple TV: Upgrade to tvOS 18.1 or later
  5. 5. For Apple Vision Pro: Upgrade to visionOS 2.1 or later
  6. 6. For Apple Watch: Upgrade to watchOS 11.1 or later
  7. 7. After upgrade, verify the new OS version is installed successfully
Caveat Standard iOS/tvOS/visionOS/watchOS upgrade considerations apply; ensure backup of important data 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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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