Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2002-1809: Default NULL Root Password in MySQL Windows Binary (3.23.2-3.23.52)

Published Jun 28, 2005 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS16.1%97th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Oracle Corporation
IdentifiersCVE-2002-1809CWE-798

The Windows binary distribution of MySQL versions 3.23.2 through 3.23.52 is shipped with a default configuration where the root account has a NULL (empty) password. This misconfiguration allows remote attackers to connect to the MySQL server as root without authentication, granting them full administrative privileges over the database.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote attackers can gain unauthorized root access to the MySQL database, allowing them to read, modify, or delete any data, create or drop databases, and potentially execute further attacks against the host system or other connected systems.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to the MySQL server to trusted hosts only, and use firewall rules to block unauthorized connections. Remove or disable the root account if not needed, and ensure all accounts have strong passwords set.

Remediation

Patch, then assume compromise.

Set a strong, non-default password for the MySQL root account immediately after installation. Upgrade to a later version of MySQL where the installer enforces root password creation or disables remote root access by default.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Oracle CorporationMysqlapplication
FAQ

Frequently asked questions

Is CVE-2002-1809 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2002-1809 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2002-1809?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2002-1809.
Is there a patch for CVE-2002-1809?
Set a strong, non-default password for the MySQL root account immediately after installation. Upgrade to a later version of MySQL where the installer enforces root password creation or disables remote root access by default.
What products are affected by CVE-2002-1809?
Oracle Corporation Mysql.
How severe is CVE-2002-1809?
CVE-2002-1809 has a CVSS v2 score of 7.5 (High) and an EPSS score of 16.1% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.