dbcve.org
ShortcutsApplication · Apple

CVE-2019-7289

MEDIUM · 5.5 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to 2.1.3 or later.
See remediation →
57/100
Remediation priority · Elevated
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 parsing issue in the handling of directory paths was addressed with improved path validation. This issue is fixed in Shortcuts 2.1.3 for iOS. A local user may be able to view senstive user information.

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

This is a path traversal vulnerability in Apple's Shortcuts app for iOS (versions prior to 2.1.3). The app's directory path parsing logic lacked proper validation, allowing a local attacker to craft malicious shortcuts that could access sensitive user information outside the intended sandbox boundaries.

MitigationUpgrade iOS Shortcuts to version 2.1.3 or later. For enterprise environments, deploy the update via MDM and verify installation across managed devices.

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
ShortcutsApplication
Affected:< 2.1.3

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 Shortcuts app version via iOS Settings
    Open Settings > General > iPhone Storage > find Shortcuts in the list and tap it. Note the Version number displayed.
    Affected if Version shown is lower than 2.1.3 (for example, 2.1.2, 2.1.1, 2.0.x, etc.)
  2. Check Shortcuts version via App Store
    Open the App Store, search for 'Shortcuts' (Apple app), tap the app, and view the version number in the app description.
    Affected if Listed version is below 2.1.3
  3. Check via MDM enterprise management console
    Use your MDM tool (such as Jamf, MobileIron, Microsoft Intune, or similar) to query installed applications on managed iOS devices. Filter for the Shortcuts app and review the reported version.
    Affected if MDM reports Shortcuts version lower than 2.1.3 on any managed device
  4. Verify iOS version as secondary context
    Check the iOS version on the device (Settings > General > About > iOS Version). This matters because Shortcuts app version availability may vary by iOS version.
    Affected if Device runs an older iOS version that restricts access to newer Shortcuts updates

If the installed Shortcuts app version is below 2.1.3, the device is affected by this path traversal 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.

From vendor data
Upgrade available Upgrade to 2.1.3 or later
Fixed in 2.1.3
Interim mitigation

Upgrade iOS Shortcuts to version 2.1.3 or later. For enterprise environments, deploy the update via MDM and verify installation across managed devices.

Fix this in Shortcuts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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