# CVE-2000-0384: Hardcoded credentials in n/a

> Remote attackers can gain root access to NetStructure devices by guessing undocumented account passwords derived from the MAC address.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-765g-qxmj-pjrx

## What is CVE-2000-0384?

CVE-2000-0384 is a critical vulnerability in n/a, published on 15 Jun 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NetStructure 7110 and 7180 have undocumented accounts (servnow, root, and wizard) whose passwords are easily guessable from the NetStructure's MAC address, which could allow remote attackers to gain root access.

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

It affects 2 products.


Products: Intel Netstructure 7110, Intel Netstructure 7180.

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

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

## Is CVE-2000-0384 being exploited?

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

Public exploit code:

- Intel Corporation NetStructure 7110 - Undocumented Password (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0384 is a critical vulnerability in n/a, published on 15 Jun 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0384 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-0384/ (Markdown: https://insights.sbomify.com/CVE-2000-0384/index.md)
```

## Sources

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

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