# CVE-2019-6321: Security feature bypass in HP Z4 G4 Core-X Workstation

> Attackers can tamper with runtime BIOS code on HP Workstations if the TPM is disabled, bypassing security protections.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9c6c-jqh5-vqv4

## What is CVE-2019-6321?

CVE-2019-6321 is a high-severity vulnerability in HP Z4 G4 Core-X Workstation, published on 29 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

HP has identified a security vulnerability with some versions of Workstation BIOS (UEFI Firmware) where the runtime BIOS code could be tampered with if the TPM is disabled. This vulnerability relates to Workstations whose TPM is disabled by default.

Weakness: CWE-667 (Improper Locking)

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

It affects 4 products.


Products: Hp Z4 G4 Core-X Workstation Firmware, Hp Z4 G4 Workstation Firmware, Hp Z6 G4 Workstation Firmware, Hp Z8 G4 Workstation Firmware.

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

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

## Is CVE-2019-6321 being exploited?

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

## Other vulnerabilities in HP Z4 G4 Core-X Workstation

- [CVE-2019-6322](https://insights.sbomify.com/CVE-2019-6322/): Security feature bypass in HP Z4 G4 Core-X Workstation (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6321 is a high-severity vulnerability in HP Z4 G4 Core-X Workstation, published on 29 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6321 in the wild and no public exploit code.

Affected product: HP Z4 G4 Core-X Workstation. 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-6321/ (Markdown: https://insights.sbomify.com/CVE-2019-6321/index.md)
```

## Sources

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

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