# CVE-2023-5739: Privilege escalation in HP PC Hardware Diagnostics Windows

> An attacker can exploit HP PC Hardware Diagnostics Windows to gain elevated privileges on the affected system.

- **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:** 31 Oct 2023
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-v5x7-5rc8-h4m4

## What is CVE-2023-5739?

CVE-2023-5739 is a high-severity vulnerability in HP PC Hardware Diagnostics Windows, published on 31 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain versions of HP PC Hardware Diagnostics Windows are potentially vulnerable to elevation of privilege.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2023-5739?

It affects 3 products.


Products: Hp Image Assistant, Hp Pc Hardware Diagnostics, Hp Thunderbolt Dock G2 Firmware.

## How do I fix CVE-2023-5739?

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

## Is CVE-2023-5739 being exploited?

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

## Other vulnerabilities in HP PC Hardware Diagnostics Windows

- [CVE-2023-32673](https://insights.sbomify.com/CVE-2023-32673/): Privilege escalation in HP PC Hardware Diagnostics Windows, HP Image Assistant, and HP Thunderbolt Dock G2 Firmware (critical 9.8)
- [CVE-2025-13492](https://insights.sbomify.com/CVE-2025-13492/): HP Image Assistant - Potential Escalation of Privilege (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5739 and fix it if it is affected.

What it is: CVE-2023-5739 is a high-severity vulnerability in HP PC Hardware Diagnostics Windows, published on 31 Oct 2023. 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-2023-5739 in the wild and no public exploit code.

Affected product: HP PC Hardware Diagnostics Windows. 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-2023-5739/ (Markdown: https://insights.sbomify.com/CVE-2023-5739/index.md)
```

## Sources

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

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