# CVE-2022-31647: Docker Desktop before 4.6.0 on Windows allows attackers to delete any file through the hyperv/destroy dockerBackendV2 API via a symlink in t


- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Apr 2023
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-hq97-x836-5mc4

## What is CVE-2022-31647?

CVE-2022-31647 is a high-severity vulnerability in n/a, published on 27 Apr 2023. 

### Official description

Docker Desktop before 4.6.0 on Windows allows attackers to delete any file through the hyperv/destroy dockerBackendV2 API via a symlink in the DataFolder parameter, a different vulnerability than CVE-2022-26659.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2022-31647?

It affects 1 product.


Products: Docker Desktop.

## How do I fix CVE-2022-31647?

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

## Is CVE-2022-31647 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-8695](https://insights.sbomify.com/CVE-2024-8695/): Code injection in Docker Desktop (critical 9.0)
- [CVE-2024-8696](https://insights.sbomify.com/CVE-2024-8696/): Code injection in Docker Desktop (high 8.9)
- [CVE-2022-37326](https://insights.sbomify.com/CVE-2022-37326/): Path traversal in n/a (high 7.8)
- [CVE-2021-37841](https://insights.sbomify.com/CVE-2021-37841/): Missing authorization in n/a (high 7.8)
- [CVE-2025-3224](https://insights.sbomify.com/CVE-2025-3224/): Elevation of Privilege in Docker Desktop for Windows during Upgrade due to Insecure Directory Deletion (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31647 and fix it if it is affected.

What it is: CVE-2022-31647 is a high-severity vulnerability in n/a, published on 27 Apr 2023. 
Exploitation: There is no known exploitation of CVE-2022-31647 in the wild and no public exploit code.

Affected product: n/a. 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-2022-31647/ (Markdown: https://insights.sbomify.com/CVE-2022-31647/index.md)
```

## Sources

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

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