# CVE-2001-0968: Hardcoded credentials in n/a

> Arkeia server installs with a null root password by default, allowing attackers to gain administrative privileges and execute code.

- **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:** 2 Feb 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-prxr-8fgv-9j7f

## What is CVE-2001-0968?

CVE-2001-0968 is a critical vulnerability in n/a, published on 2 Feb 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Knox Arkeia server 4.2, and possibly other versions, installs its root user with a null password by default, which allows local and remote users to gain privileges.

## Which versions are affected by CVE-2001-0968?

It affects 1 product.


Products: Knox Software Arkeia.

## How do I fix CVE-2001-0968?

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

## Is CVE-2001-0968 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0988](https://insights.sbomify.com/CVE-2001-0988/): Misconfiguration in n/a (high 7.2)
- [CVE-1999-1534](https://insights.sbomify.com/CVE-1999-1534/): Memory corruption in n/a (high 7.2)
- [CVE-1999-0788](https://insights.sbomify.com/CVE-1999-0788/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0968 and fix it if it is affected.

What it is: CVE-2001-0968 is a critical vulnerability in n/a, published on 2 Feb 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2001-0968 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-2001-0968/ (Markdown: https://insights.sbomify.com/CVE-2001-0968/index.md)
```

## Sources

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

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