# CVE-2021-3919: Privilege escalation in OMEN Gaming Hub and HP Command Center

> Attackers can escalate privileges or cause denial of service in HP OMEN Gaming Hub and HP Command Center via a vulnerability requiring software updates.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-2xvx-8cff-qx52

## What is CVE-2021-3919?

CVE-2021-3919 is a critical vulnerability in OMEN Gaming Hub and HP Command Center, published on 21 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A potential security vulnerability has been identified in OMEN Gaming Hub and in HP Command Center which may allow escalation of privilege and/or denial of service. HP has released software updates to mitigate the potential vulnerability.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2021-3919?

It affects 2 products.


Products: Hp Command Center, Hp Omen Gaming Hub.

## How do I fix CVE-2021-3919?

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

## Is CVE-2021-3919 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3919 and fix it if it is affected.

What it is: CVE-2021-3919 is a critical vulnerability in OMEN Gaming Hub and HP Command Center, published on 21 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-3919 in the wild and no public exploit code.

Affected product: OMEN Gaming Hub and HP Command Center. 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-2021-3919/ (Markdown: https://insights.sbomify.com/CVE-2021-3919/index.md)
```

## Sources

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

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