# CVE-2000-0276: Denial of service in n/a

> Local attackers can cause a denial of service in BeOS by issuing malformed direct system calls via interrupt 37.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **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:** 22 Jan 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wwrg-82fc-4xc8

## What is CVE-2000-0276?

CVE-2000-0276 is a low-severity denial of service 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

BeOS 4.5 and 5.0 allow local users to cause a denial of service via malformed direct system calls using interrupt 37.

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

It affects 1 product.


Products: Be Beos.

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

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

## Is CVE-2000-0276 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0276 exists.

Public exploit code:

- Be BeOS 4.5/5.0 - Invalid System Call (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0305](https://insights.sbomify.com/CVE-2000-0305/): Denial of service in n/a (high 7.8)
- [CVE-2000-1152](https://insights.sbomify.com/CVE-2000-1152/): Denial of service in n/a (medium 5.0)
- [CVE-2000-0279](https://insights.sbomify.com/CVE-2000-0279/): Denial of service in n/a (medium 5.0)
- [CVE-2000-0463](https://insights.sbomify.com/CVE-2000-0463/): BeOS 5.0 allows remote attackers to cause a denial of service via fragmented TCP packets. (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0276 is a low-severity denial of service 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0276 exists.

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-0276/ (Markdown: https://insights.sbomify.com/CVE-2000-0276/index.md)
```

## Sources

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

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