CVE-2002-1809: High severity oracle mysql vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Set a secure, non-NULL password for the MySQL 'root' account on affected Windows binary releases (3.23.2 through 3.23.52). For example, from the command line: mysqladmin -u root password 'YourNewStrongPassword' or, from within MySQL: UPDATE mysql.user SET Password = PASSWORD('YourNewStrongPassword') WHERE User = 'root'; FLUSH PRIVILEGES;
MySQL (Windows binary release 3.23.2 through 3.23.52) root password = set to a non-NULL (non-empty) strong password
Event History
Frequently Asked Questions
What is the severity of CVE-2002-1809?
CVE-2002-1809 is classified as a high severity vulnerability due to the presence of a NULL root password allowing unauthorized remote access.
How do I fix CVE-2002-1809?
To fix CVE-2002-1809, set a strong root password for MySQL in your database configuration.
What versions of MySQL are affected by CVE-2002-1809?
CVE-2002-1809 affects MySQL versions 3.23.2 through 3.23.52.
Can CVE-2002-1809 be exploited remotely?
Yes, CVE-2002-1809 can be exploited remotely due to the default NULL root password.
What are the consequences of CVE-2002-1809?
The consequences of CVE-2002-1809 include unauthorized access to the MySQL database, which may lead to data breaches and other security risks.