# CVE-2019-14743: Privilege escalation in n/a

> Local attackers can escalate privileges to SYSTEM due to insecure registry permissions in the Steam Client for Windows.

- **Severity:** Medium 6.6 (`CVSS:3.0/AV:P/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:** 7 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-377c-pvc8-rpq3

## What is CVE-2019-14743?

CVE-2019-14743 is a medium-severity vulnerability in n/a, published on 7 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Valve Steam Client for Windows through 2019-08-07, HKLM\SOFTWARE\Wow6432Node\Valve\Steam has explicit "Full control" for the Users group, which allows local users to gain NT AUTHORITY\SYSTEM access.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Valvesoftware Steam Client.

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

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

## Is CVE-2019-14743 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-30481](https://insights.sbomify.com/CVE-2021-30481/): Memory corruption in n/a (high 8.0)
- [CVE-2020-15530](https://insights.sbomify.com/CVE-2020-15530/): Race condition in n/a (high 7.8)
- [CVE-2019-17180](https://insights.sbomify.com/CVE-2019-17180/): Path traversal in n/a (high 7.8)
- [CVE-2019-15315](https://insights.sbomify.com/CVE-2019-15315/): Privilege escalation in n/a (high 7.8)
- [CVE-2015-7985](https://insights.sbomify.com/CVE-2015-7985/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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