# CVE-2017-5873: Privilege escalation in n/a

> Local attackers can gain privileges by placing a malicious executable in the system drive due to an unquoted search path in the guest service.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3pg9-h44j-gvg9

## What is CVE-2017-5873?

CVE-2017-5873 is a medium-severity vulnerability in n/a, published on 11 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unquoted Windows search path vulnerability in the guest service in Unisys s-Par before 4.4.20 allows local users to gain privileges via a Trojan horse executable file in the %SYSTEMDRIVE% directory, as demonstrated by program.exe.

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

## Which versions are affected by CVE-2017-5873?

It affects 1 product.


Products: Unisys Secure Partitioning.

## How do I fix CVE-2017-5873?

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

## Is CVE-2017-5873 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5873 and fix it if it is affected.

What it is: CVE-2017-5873 is a medium-severity vulnerability in n/a, published on 11 Apr 2017. 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-2017-5873 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-2017-5873/ (Markdown: https://insights.sbomify.com/CVE-2017-5873/index.md)
```

## Sources

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

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