# CVE-2019-7289: Path traversal in Shortcuts

> A local attacker can exploit a path parsing flaw in the iOS Shortcuts app to view sensitive user information.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8453-jjmp-9q2q

## What is CVE-2019-7289?

CVE-2019-7289 is a medium-severity path traversal vulnerability in Apple Shortcuts, published on 18 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-7289?

It affects 1 product.


Products: Apple Shortcuts.

## How do I fix CVE-2019-7289?

No fix has been published for CVE-2019-7289 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-7289 being exploited?

There is no known exploitation of CVE-2019-7289 in the wild and no public exploit code.

## Other vulnerabilities in Apple Shortcuts

- [CVE-2019-7290](https://insights.sbomify.com/CVE-2019-7290/): Security feature bypass in Shortcuts (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7289 and fix it if it is affected.

What it is: CVE-2019-7289 is a medium-severity path traversal vulnerability in Apple Shortcuts, published on 18 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7289 in the wild and no public exploit code.

Affected product: Apple Shortcuts. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-7289/ (Markdown: https://insights.sbomify.com/CVE-2019-7289/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-7289
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-7289
- OSV: https://osv.dev/vulnerability/CVE-2019-7289

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-7289/
Summaries are generated and may contain mistakes; the official description above is the record.