# CVE-2000-0402: Information disclosure in n/a

> Local attackers can read plaintext admin credentials from log files in mixed-mode SQL Server, enabling privilege escalation.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 12 Jul 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wr9w-p9gv-6q7p

## What is CVE-2000-0402?

CVE-2000-0402 is a low-severity vulnerability in Microsoft Sql Server, published on 12 Jul 2000. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Mixed Mode authentication capability in Microsoft SQL Server 7.0 stores the System Administrator (sa) account in plaintext in a log file which is readable by any user, aka the "SQL Server 7.0 Service Pack Password" vulnerability.

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

It affects 1 product.


Products: Microsoft Sql Server.

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

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

## Is CVE-2000-0402 being exploited?

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

Public exploit code:

- Microsoft SQL Server Payload Execution (metasploit)
- Microsoft SQL Server Payload Execution via SQL Injection (metasploit)
- Microsoft SQL Server - Payload Execution (Metasploit) (exploitdb)
- Microsoft SQL Server - Payload Execution (via SQL Injection) (Metasploit) (exploitdb)

## Other vulnerabilities in Microsoft Sql Server

- [CVE-2020-0618](https://insights.sbomify.com/CVE-2020-0618/): Microsoft SQL Server Reporting Services Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-1068](https://insights.sbomify.com/CVE-2019-1068/): Microsoft SQL Server Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2018-8273](https://insights.sbomify.com/CVE-2018-8273/): Memory corruption in Microsoft SQL Server (critical 9.8)
- [CVE-2008-5416](https://insights.sbomify.com/CVE-2008-5416/): Memory corruption in n/a (critical 9.0)
- [CVE-2023-21705](https://insights.sbomify.com/CVE-2023-21705/): Microsoft SQL Server Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0402 is a low-severity vulnerability in Microsoft Sql Server, published on 12 Jul 2000. 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-0402 exists.

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

## Sources

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

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