# CVE-2002-1809: Hardcoded credentials in n/a

> Remote attackers can gain unauthorized root access to MySQL databases due to a default NULL root password in the Windows binary release.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wmgc-gwrp-pgcv

## What is CVE-2002-1809?

CVE-2002-1809 is a high-severity vulnerability in Oracle Mysql, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of the Windows binary release of MySQL 3.23.2 through 3.23.52 has a NULL root password, which could allow remote attackers to gain unauthorized root access to the MySQL database.

## Which versions are affected by CVE-2002-1809?

It affects 1 product.


Products: Oracle Mysql.

## How do I fix CVE-2002-1809?

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

## Is CVE-2002-1809 being exploited?

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

Public exploit code:

- MySQL 3.20.32/3.22.x/3.23.x - Null Root Password Weak Default Configuration (1) (exploitdb)

## Other vulnerabilities in Oracle Mysql

- [CVE-2016-0639](https://insights.sbomify.com/CVE-2016-0639/): Auth bypass in n/a (critical 9.8)
- [CVE-2003-0150](https://insights.sbomify.com/CVE-2003-0150/): Privilege escalation in n/a (critical 9.0)
- [CVE-2005-2572](https://insights.sbomify.com/CVE-2005-2572/): Denial of service in n/a (high 8.5)
- [CVE-2020-14878](https://insights.sbomify.com/CVE-2020-14878/): Auth bypass in MySQL Server (high 8.0)
- [CVE-2002-0969](https://insights.sbomify.com/CVE-2002-0969/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1809 and fix it if it is affected.

What it is: CVE-2002-1809 is a high-severity vulnerability in Oracle Mysql, published on 28 Jun 2005. 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-2002-1809 exists.

Affected product: Oracle Mysql. 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-2002-1809/ (Markdown: https://insights.sbomify.com/CVE-2002-1809/index.md)
```

## Sources

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

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