# CVE-2020-9858: Path traversal in Windows Migration Assistant

> Running the installer in an untrusted directory allows arbitrary code execution due to dynamic library loading issues.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8v24-3r89-xw58

## What is CVE-2020-9858?

CVE-2020-9858 is a high-severity path traversal vulnerability in Apple Windows Migration Assistant, published on 9 Jun 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A dynamic library loading issue was addressed with improved path searching. This issue is fixed in Windows Migration Assistant 2.2.0.0 (v. 1A11). Running the installer in an untrusted directory may result in arbitrary code execution.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2020-9858?

It affects 1 product.


Products: Apple Windows Migration Assistant.

## How do I fix CVE-2020-9858?

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

## Is CVE-2020-9858 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9858 and fix it if it is affected.

What it is: CVE-2020-9858 is a high-severity path traversal vulnerability in Apple Windows Migration Assistant, published on 9 Jun 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-9858 in the wild and no public exploit code.

Affected product: Apple Windows Migration Assistant. 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-2020-9858/ (Markdown: https://insights.sbomify.com/CVE-2020-9858/index.md)
```

## Sources

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

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