CVE-2003-1480: Medium severity MySQL mysql vulnerability
Published Dec 31, 2003
·Updated
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.
Affected Software
66 affected components
MySQL mysql=4.1.0
Oracle MySQL=3.20
Oracle MySQL=3.20.32a
Oracle MySQL=3.21
Oracle MySQL=3.22
Oracle MySQL=3.22.26
Oracle MySQL=3.22.27
Oracle MySQL=3.22.28
Oracle MySQL=3.22.29
Oracle MySQL=3.23.10
Oracle MySQL=3.23.22
Oracle MySQL=3.23.24
Oracle MySQL=3.23.28-gamma
Oracle MySQL=3.23.3
Oracle MySQL=3.23.8
Oracle MySQL=3.22.30
Oracle MySQL=3.22.32
Oracle MySQL=3.23.5
Oracle MySQL=3.23.25
Oracle MySQL=3.23.26
Oracle MySQL=3.23.27
Oracle MySQL=3.23.28
Oracle MySQL=3.23.4
Oracle MySQL=3.23.2
Oracle MySQL=3.23.23
Oracle MySQL=3.23.29
Oracle MySQL=3.23.9
Oracle MySQL=3.23.36
Oracle MySQL=3.23.38
Oracle MySQL=3.23.44
Oracle MySQL=3.23.46
Oracle MySQL=3.23.50
Oracle MySQL=3.23.52
Oracle MySQL=4.0.0
Oracle MySQL=4.0.8-gamma
Oracle MySQL=3.23.31
Oracle MySQL=3.23.32
Oracle MySQL=3.23.33
Oracle MySQL=3.23.34
Oracle MySQL=3.23.47
Oracle MySQL=3.23.48
Oracle MySQL=3.23.49
Oracle MySQL=4.0.1
Oracle MySQL=4.0.2
Oracle MySQL=4.0.3
Oracle MySQL=4.0.5a
Oracle MySQL=3.23.39
Oracle MySQL=3.23.40
Oracle MySQL=3.23.41
Oracle MySQL=3.23.42
Oracle MySQL=3.23.53a
Oracle MySQL=3.23.54
Oracle MySQL=3.23.54a
Oracle MySQL=3.23.55
Oracle MySQL=3.23.30
Oracle MySQL=3.23.35
Oracle MySQL=3.23.37
Oracle MySQL=3.23.43
Oracle MySQL=3.23.45
Oracle MySQL=3.23.51
Oracle MySQL=3.23.53
Oracle MySQL=3.23.56
Oracle MySQL=4.0.7-gamma
Oracle MySQL=4.0.11-gamma
Oracle MySQL=4.1.0-alpha
Oracle MySQL=4.0.9-gamma
Event History
Dec 31, 2003
CVE Published
05:00 AM
Data Sourced
via NVD·05:00 AM
DescriptionSeverityWeaknessAffected Software
Oct 24, 2007
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2003-1480?
CVE-2003-1480 is considered a high severity vulnerability due to the weak hashing algorithm of passwords in MySQL.
2
How do I fix CVE-2003-1480?
To fix CVE-2003-1480, upgrade MySQL to a version that uses a stronger password hashing algorithm.
3
Which versions of MySQL are affected by CVE-2003-1480?
CVE-2003-1480 affects MySQL versions 3.20 through 4.1.0, including multiple specific versions within that range.
4
What is the impact of CVE-2003-1480?
The impact of CVE-2003-1480 includes the increased risk of password compromise due to its ease of decryption using brute force methods.
5
Is there a patch available for CVE-2003-1480?
No specific patch is provided for CVE-2003-1480; the recommended action is to upgrade to a secure version of MySQL.