# CVE-2022-37018: Privilege escalation in HP PC BIOS

> A vulnerability in HP PC BIOS allows attackers to escalate privileges and execute code, requiring firmware updates for mitigation.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-vv23-8mw3-7r7r

## What is CVE-2022-37018?

CVE-2022-37018 is a high-severity vulnerability in HP PC BIOS, published on 21 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential vulnerability has been identified in the system BIOS for certain HP PC products which may allow escalation of privileges and code execution. HP is releasing firmware updates to mitigate the potential vulnerability.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2022-37018?

It affects 75 products.


Products: Hp Elite Slice Firmware, Hp Elite X2 1012 G1 Firmware, Hp Elite X2 1012 G2 Firmware, Hp Elitebook 1030 G1 Firmware, Hp Elitebook 1040 G3 Firmware, Hp Elitebook 1040 G4 Firmware, Hp Elitebook 820 G3 Firmware, Hp Elitebook 820 G4 Firmware, Hp Elitebook 828 G3 Firmware, Hp Elitebook 828 G4 Firmware, Hp Elitebook 840 G3 Firmware, Hp Elitebook 840 G4 Firmware, Hp Elitebook 848 G3 Firmware, Hp Elitebook 848 G4 Firmware, Hp Elitebook 850 G3 Firmware, Hp Elitebook 850 G4 Firmware, Hp Elitebook Folio G1 Firmware, Hp Elitebook X360 1020 G2 Firmware, Hp Elitebook X360 1030 G2 Firmware, Hp Elitedesk 800 35w G2 Desktop Mini Pc Firmware and 55 more.

## How do I fix CVE-2022-37018?

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

## Is CVE-2022-37018 being exploited?

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

## Other vulnerabilities in HP PC BIOS

- [CVE-2022-37019](https://insights.sbomify.com/CVE-2022-37019/): HP PC BIOS May 2024 Security Updates for Potential Stack Buffer Overflows (medium 6.8)
- [CVE-2022-37020](https://insights.sbomify.com/CVE-2022-37020/): HP PC BIOS May 2024 Security Updates for Potential Stack Buffer Overflows (medium 6.8)
- [CVE-2019-18618](https://insights.sbomify.com/CVE-2019-18618/): Missing authorization in n/a (medium 6.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37018 and fix it if it is affected.

What it is: CVE-2022-37018 is a high-severity vulnerability in HP PC BIOS, published on 21 Nov 2022. 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-2022-37018 in the wild and no public exploit code.

Affected product: HP PC BIOS. 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-2022-37018/ (Markdown: https://insights.sbomify.com/CVE-2022-37018/index.md)
```

## Sources

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

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