# CVE-2022-23909: Privilege escalation in n/a

> Local attackers can escalate privileges by exploiting an unquoted service path in Sherpa Connector Service to execute arbitrary code.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-634r-5wp4-57x4

## What is CVE-2022-23909?

CVE-2022-23909 is a high-severity vulnerability in n/a, published on 5 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an unquoted service path in Sherpa Connector Service (SherpaConnectorService.exe) 2020.2.20328.2050. This might allow a local user to escalate privileges by creating a "C:\Program Files\Sherpa Software\Sherpa.exe" file.

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

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

It affects 1 product.


Products: Gimmal Sherpa Connector Service.

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

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

## Is CVE-2022-23909 being exploited?

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

Public exploit code:

- Unquoted Service Path privilege escalation vulnerability in Sherpa Connector Service.  (github_poc): https://github.com/netsectuna/CVE-2022-23909
- Sherpa Connector Service v2020.2.20328.2050 - Unquoted Service Path (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23909 is a high-severity vulnerability in n/a, published on 5 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23909 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-23909/ (Markdown: https://insights.sbomify.com/CVE-2022-23909/index.md)
```

## Sources

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

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