# CVE-2022-46330: Other in Installers generated by Squirrel.Windows

> Attackers can execute arbitrary code via DLL hijacking in Squirrel.Windows installers due to insecure DLL search paths.

- **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:** 21 Dec 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-hg2g-2j5v-39rv

## What is CVE-2022-46330?

CVE-2022-46330 is a high-severity vulnerability in Installers generated by Squirrel.Windows, published on 21 Dec 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

Squirrel.Windows is both a toolset and a library that provides installation and update functionality for Windows desktop applications. Installers generated by Squirrel.Windows 2.0.1 and earlier contain an issue with the DLL search path, which may lead to insecurely loading Dynamic Link Libraries. As a result, arbitrary code may be executed with the privilege of the user invoking the installer.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Squirrel.windows Project Squirrel.windows.

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

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

## Is CVE-2022-46330 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46330 is a high-severity vulnerability in Installers generated by Squirrel.Windows, published on 21 Dec 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-46330 in the wild and no public exploit code.

Affected product: Installers generated by Squirrel.Windows. 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-46330/ (Markdown: https://insights.sbomify.com/CVE-2022-46330/index.md)
```

## Sources

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

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