# CVE-2019-6173: Privilege escalation in Installation Packages

> Attackers with administrative privileges can escalate privileges via DLL search path vulnerability in Lenovo installation packages.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jun 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vxgg-fjmf-6j33

## What is CVE-2019-6173?

CVE-2019-6173 is a medium-severity vulnerability in Lenovo Installation Packages, published on 9 Jun 2020. 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

A DLL search path vulnerability could allow privilege escalation in some Lenovo installation packages, prior to version 1.2.9.3, during installation if an attacker already has administrative privileges.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2019-6173?

It affects 1 product.


Products: Lenovo Installation Package.

## How do I fix CVE-2019-6173?

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

## Is CVE-2019-6173 being exploited?

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

## Other vulnerabilities in Lenovo Installation Packages

- [CVE-2019-6196](https://insights.sbomify.com/CVE-2019-6196/): Path traversal in Installation Packages (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6173 and fix it if it is affected.

What it is: CVE-2019-6173 is a medium-severity vulnerability in Lenovo Installation Packages, published on 9 Jun 2020. 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-2019-6173 in the wild and no public exploit code.

Affected product: Lenovo Installation Packages. 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-2019-6173/ (Markdown: https://insights.sbomify.com/CVE-2019-6173/index.md)
```

## Sources

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

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