# CVE-2022-27966: Code injection in n/a

> Attackers can execute arbitrary code on systems running Xshell by exploiting a binary hijack vulnerability via a crafted executable file.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-85m7-w6gg-59m8

## What is CVE-2022-27966?

CVE-2022-27966 is a medium-severity code injection vulnerability in n/a, published on 31 Mar 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

Xshell v7.0.0099 and below contains a binary hijack vulnerability which allows attackers to execute arbitrary code via a crafted .exe file.

Weakness: CWE-428 (Unquoted Search Path or Element)

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

It affects 1 product.


Products: Netsarang Xshell.

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

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

## Is CVE-2022-27966 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-42095](https://insights.sbomify.com/CVE-2021-42095/): Denial of service in n/a (high 7.5)
- [CVE-2021-37326](https://insights.sbomify.com/CVE-2021-37326/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27966 is a medium-severity code injection vulnerability in n/a, published on 31 Mar 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-27966 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-27966/ (Markdown: https://insights.sbomify.com/CVE-2022-27966/index.md)
```

## Sources

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

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