# CVE-2000-0946: Security feature bypass in n/a

> Attackers can bypass screen lock to execute programs or gain privileges via Compaq Easy Access Keyboard custom buttons.

- **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:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vvw3-w5g2-3864

## What is CVE-2000-0946?

CVE-2000-0946 is a medium-severity vulnerability in n/a, published on 22 Jan 2001. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Compaq Easy Access Keyboard software 1.3 does not properly disable access to custom buttons when the screen is locked, which could allow an attacker to gain privileges or execute programs without authorization.

## Which versions are affected by CVE-2000-0946?

It affects 1 product.


Products: Compaq Easy Access Keyboard Software.

## How do I fix CVE-2000-0946?

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

## Is CVE-2000-0946 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0946 and fix it if it is affected.

What it is: CVE-2000-0946 is a medium-severity vulnerability in n/a, published on 22 Jan 2001. 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-2000-0946 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-2000-0946/ (Markdown: https://insights.sbomify.com/CVE-2000-0946/index.md)
```

## Sources

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

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