# CVE-2022-24767: Other in Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)

> Git for Windows uninstaller allows DLL hijacking when run as SYSTEM, enabling local privilege escalation and code execution.

- **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:** 12 Apr 2022
- **Updated:** 1 Oct 2024

## What is CVE-2022-24767?

CVE-2022-24767 is a high-severity vulnerability in Microsoft Visual Studio 2017, published on 12 Apr 2022. 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

GitHub: Git for Windows' uninstaller vulnerable to DLL hijacking when run under the SYSTEM user account.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 4 products.


Products: Git for Windows Project Git for Windows, Microsoft Visual Studio 2017, Microsoft Visual Studio 2019, Microsoft Visual Studio 2022.

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

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

## Is CVE-2022-24767 being exploited?

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

## Other vulnerabilities in Microsoft Visual Studio 2017

- [CVE-2023-23618](https://insights.sbomify.com/CVE-2023-23618/): gitk can inadvertently call executables in the worktree (high 8.6)
- [CVE-2016-9274](https://insights.sbomify.com/CVE-2016-9274/): Privilege escalation in n/a (high 7.8)
- [CVE-2023-29011](https://insights.sbomify.com/CVE-2023-29011/): Git for Windows's config file of `connect.exe` is susceptible to malicious placing (high 7.6)
- [CVE-2023-29012](https://insights.sbomify.com/CVE-2023-29012/): Git CMD erroneously executes `doskey.exe` in the current directory, if it exists (high 7.3)
- [CVE-2023-22743](https://insights.sbomify.com/CVE-2023-22743/): Git for Windows' installer is susceptible to DLL side loading attacks (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24767 is a high-severity vulnerability in Microsoft Visual Studio 2017, published on 12 Apr 2022. 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-2022-24767 in the wild and no public exploit code.

Affected product: Microsoft Visual Studio 2017. 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-24767/ (Markdown: https://insights.sbomify.com/CVE-2022-24767/index.md)
```

## Sources

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

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