CVE-2022-23909 json
There is an unquoted service path in Sherpa Connector Service (SherpaConnectorService.exe) 2020.2.20328.2050.
published 4y ago modified 4mo ago also EUVD-2022-28831
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 1
- Exploit-DB
Summary
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.
Is CVE-2022-23909 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-50852)
Exploit prediction
1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-50852 Sherpa Connector Service v2020.2.20328.2050 - Unquoted Service Path local, 2022-04-07
- packetstormsecurity.com http://packetstormsecurity.com/files/166574/Sherpa-Connector-Service-2020.2.20328.2050-Unquoted-Service-Path.html referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/netsectuna/CVE-2022-23909 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-428 Unquoted Search Path or Element
References
-
packetstormsecurity.com
/files/166574/Sherpa-Connector-Service-2020.2.20328.2050-Unquoted-Service-Path.html
exploit, third-party-advisory, vdb-entry
-
github.com
/netsectuna/CVE-2022-23909
exploit, third-party-advisory
Sources
- CVE List CVE-2022-23909
- NVD CVE-2022-23909
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.