# CVE-2005-0963: Denial of service in n/a

> A flaw in Toshiba ACPI BIOS prevents booting if the active partition is not in the first MBR slot, requiring administrative access to trigger.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **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:** 3 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r3gm-hf7r-pmjr

## What is CVE-2005-0963?

CVE-2005-0963 is a low-severity denial of service vulnerability in n/a, published on 3 Apr 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An error in the Toshiba ACPI BIOS 1.6 causes the BIOS to only examine the first slot in the Master Boot Record (MBR) table for an active partition, which prevents the system from booting even though the MBR is not malformed.  NOTE: it has been debated as to whether or not this issue poses a security vulnerability, since administrative privileges would be required, and other DoS attacks are possible with such privileges.

## Which versions are affected by CVE-2005-0963?

It affects 1 product.


Products: Toshiba Acpi Flash Bios.

## How do I fix CVE-2005-0963?

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

## Is CVE-2005-0963 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0963 and fix it if it is affected.

What it is: CVE-2005-0963 is a low-severity denial of service vulnerability in n/a, published on 3 Apr 2005. 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-2005-0963 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-2005-0963/ (Markdown: https://insights.sbomify.com/CVE-2005-0963/index.md)
```

## Sources

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

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