# CVE-2002-2059: Security feature bypass in n/a

> Local users can bypass BIOS password restrictions to change the boot device via the F8 key on affected Intel motherboards.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jul 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rhp3-rf73-5hpc

## What is CVE-2002-2059?

CVE-2002-2059 is a medium-severity vulnerability in n/a, published on 14 Jul 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

BIOS D845BG, D845HV, D845PT and D845WN on Intel motherboards does not properly restrict access to configuration information when BIOS passwords are enabled, which could allow local users to change the default boot device via the F8 key.

## Which versions are affected by CVE-2002-2059?

It affects 4 products.


Products: Intel D845bg Motherboard, Intel D845hv Motherboard, Intel D845pt Motherboard, Intel D845wn Motherboard.

## How do I fix CVE-2002-2059?

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

## Is CVE-2002-2059 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2059 and fix it if it is affected.

What it is: CVE-2002-2059 is a medium-severity vulnerability in n/a, published on 14 Jul 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-2059 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-2002-2059/ (Markdown: https://insights.sbomify.com/CVE-2002-2059/index.md)
```

## Sources

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

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