VendorsOraclemysql3.20.32a
Vulnerabilities

Oracle MySQL 3.20.32a

Ranked by severity, then by exploit likelihood. Click a CVE ID for its full record.

6CVEs
CVE-2002-1921
The default configuration of MySQL 3.20.32 through 3.23.52, when running on Windows, does set the bind address to the loopback interface, which allows remote attackers to connect to the database.
Published 2005-06-28 · Modified
7.5EPSS 0.025
CVE-2002-1923
The default configuration in MySQL 3.20.32 through 3.23.52, when running on Windows, does not have logging enabled, which could allow remote attackers to conduct activities without detection.
Published 2005-06-28 · Modified
7.5EPSS 0.025
CVE-2004-0957
Unknown vulnerability in MySQL 3.23.58 and earlier, when a local user has privileges for a database whose name includes a "_" (underscore), grants privileges to other databases that have similar names, which can allow the user to conduct unauthorized activities.
Published 2004-10-21 · Modified
6.8EPSS 0.024
CVE-2003-1480
MySQL 3.20 through 4.1.0 uses a weak algorithm for hashed passwords, which makes it easier for attackers to decrypt the password via brute force methods.
Published 2007-10-24 · Modified
4.31 PoCEPSS 0.027
CVE-2012-1696
Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.5.19 and earlier allows remote authenticated users to affect availability via unknown vectors related to Server Optimizer.
Published 2012-05-03 · Modified
4.0EPSS 0.019
CVE-2004-0381
mysqlbug in MySQL allows local users to overwrite arbitrary files via a symlink attack on the failed-mysql-bugreport temporary file.
Published 2004-04-06 · Modified
2.1EPSS 0.006