# CVE-2008-0211: Denial of service in n/a

> Local attackers can cause a denial of service on HP Compaq Business Notebooks via unspecified BIOS vectors.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pgfj-6vh7-8ffh

## What is CVE-2008-0211?

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

### Official description

Unspecified vulnerability in the BIOS F.04 through F.11 for the HP Compaq Business Notebook PC allows local users to cause a denial of service via unspecified vectors.

## Which versions are affected by CVE-2008-0211?

It affects 13 products.


Products: Compaq 2210 Series Bios, Compaq 2510 Series Bios, Compaq 2710 Series Bios, Compaq 6510 Series Bios, Compaq 6515 Series Bios, Compaq 6520 Series Bios, Compaq 6710 Series Bios, Compaq 6715 Series Bios, Compaq 6720 Series Bios, Compaq 6820 Series Bios, Compaq 6910 Series Bios, Compaq 8510 Series Bios, Compaq 8710 Series Bios.

## How do I fix CVE-2008-0211?

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

## Is CVE-2008-0211 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0211 and fix it if it is affected.

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

## Sources

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

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