dbcve.org
IpadosOperating system · Apple

CVE-2024-44255

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 →
81/100
Remediation priority · High
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
A path handling issue was addressed with improved logic. This issue is fixed in 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. A malicious app may be able to run arbitrary shortcuts without user consent.

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 path handling vulnerability in Apple's operating systems allows a malicious application to bypass user consent mechanisms and execute arbitrary shortcuts without permission. The flaw involves improper path validation that could be exploited to invoke shortcuts programmatically.

MitigationApply the available software updates (iOS 18.1, 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) to address the path handling flaw.

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.1
Iphone OsOperating system
Affected:< 18.1
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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 or iPadOS version
    Go to Settings > General > About > Version and note the version number (e.g., 17.7.1, 18.0)
    Affected if The version is below 18.1 (e.g., 17.x, 18.0)
  2. Check macOS version
    Run 'sw_vers -productVersion' in Terminal, or go to System Settings > About > macOS Version
    Affected if The version is 13.7.0 or earlier, or 14.0 through 14.7.0 (not 14.7.1 or later, and not 13.7.1 or later)
  3. Check tvOS version
    Go to Settings > General > About > Version on the Apple TV device
    Affected if The version is below 18.1
  4. Check watchOS version
    Open the Watch app on iPhone, go to My Watch > General > About, or go to Settings > General > About on the Apple Watch
    Affected if The version is below 11.1
  5. Check visionOS version
    Go to Settings > General > About > Version on the Vision Pro device
    Affected if The version is below 2.1

If the installed OS version is lower than 18.1 for iOS/iPadOS/tvOS/watchOS/visionOS, or lower than 13.7.1/14.7.1 for macOS, the device is running a vulnerable version.

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 available software updates (iOS 18.1, 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) to address the path handling flaw.

Recommended fix High confidence

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 (depending on device type)

  1. Determine the current operating system version on the affected device (Settings > General > About on iOS/iPadOS, System Settings > General > About on macOS, etc.)
  2. For iPhone or iPad: Upgrade to iOS 18.1 or iPadOS 18.1 respectively
  3. For Mac: Upgrade to macOS Ventura 13.7.1, macOS Sonoma 14.7.1, or macOS Sequoia 15.1 depending on your current major version
  4. For Apple TV: Upgrade to tvOS 18.1
  5. For Apple Vision Pro: Upgrade to visionOS 2.1
  6. For Apple Watch: Upgrade to watchOS 11.1
  7. After upgrading, verify the version number matches the fixed release to confirm the patch was applied
Caveat Standard OS upgrade considerations apply - review Apples release notes for any feature or behavior changes before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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