# CVE-2016-2243: Denial of service in n/a

> Local attackers with administrative access can cause BIOS recovery failure, leading to denial of service on HP Commercial PCs.

- **Severity:** High 7.9 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h8g3-63cv-v336

## What is CVE-2016-2243?

CVE-2016-2243 is a high-severity denial of service vulnerability in n/a, published on 4 Mar 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sure Start on HP Commercial PCs 2015 allows local users to cause a denial of service (BIOS recovery failure) by leveraging administrative access.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-2243?

It affects 7 products.


Products: Hp 1000 Series Firmware, Hp 700 Series Firmware, Hp 800 Series Firmware, Hp Elitebook Folio 1012 X2 G2, Hp Z238 Firmware, Hp Z240 Firmware, Hp Zbook Firmware.

## How do I fix CVE-2016-2243?

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

## Is CVE-2016-2243 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2243 and fix it if it is affected.

What it is: CVE-2016-2243 is a high-severity denial of service vulnerability in n/a, published on 4 Mar 2016. 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-2016-2243 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-2016-2243/ (Markdown: https://insights.sbomify.com/CVE-2016-2243/index.md)
```

## Sources

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

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