# CVE-2000-0313: Privilege escalation in n/a

> A local user can modify interface media configurations in OpenBSD, potentially leading to privilege escalation.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/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:** 7 May 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-84m3-hwqx-qqwm

## What is CVE-2000-0313?

CVE-2000-0313 is a medium-severity vulnerability in Openbsd Openbsd, published on 7 May 2001. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in OpenBSD 2.6 allows a local user to change interface media configurations.

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

It affects 1 product.


Products: Openbsd Openbsd.

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

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

## Is CVE-2000-0313 being exploited?

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

## Other vulnerabilities in Openbsd Openbsd

- [CVE-2007-1365](https://insights.sbomify.com/CVE-2007-1365/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0220](https://insights.sbomify.com/CVE-2004-0220/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0083](https://insights.sbomify.com/CVE-2004-0083/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0084](https://insights.sbomify.com/CVE-2004-0084/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0284](https://insights.sbomify.com/CVE-2001-0284/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0313 is a medium-severity vulnerability in Openbsd Openbsd, published on 7 May 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-0313 in the wild and no public exploit code.

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

## Sources

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

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