CVE-2010-1626: Low severity MySQL mysql vulnerability
Published May 21, 2010
·Updated
MySQL before 5.1.46 allows local users to delete the data and index files of another user's MyISAM table via a symlink attack in conjunction with the DROP TABLE command, a different vulnerability than CVE-2008-4098 and CVE-2008-7247.
Affected Software
50 affected components
MySQL mysql<=5.1.45
MySQL mysql=5.1.23
MySQL mysql=5.0.84
MySQL mysql=5.0.15
MySQL mysql=5.1.34
MySQL mysql=5.0.17
MySQL mysql=5.0.5.0.21
MySQL mysql=5.0.24
MySQL mysql=5.0.87
MySQL mysql=5.1.37
MySQL mysql=5.0.20
MySQL mysql=5.1.31
MySQL mysql=5.0.82
MySQL mysql=5.1.32
MySQL mysql=5.0.16
MySQL mysql=5.0.45b
MySQL mysql=5.1.5
Oracle MySQL=5.1.39
Oracle MySQL=5.1.40
Oracle MySQL=5.1.41
Oracle MySQL=5.1.42
Oracle MySQL=5.1.43
Oracle MySQL=5.1.44
Oracle MySQL=5.0.51
Oracle MySQL=5.0.18
Oracle MySQL=5.0.19
Oracle MySQL=5.0.21
Oracle MySQL=5.0.22
Oracle MySQL=5.0.23
Oracle MySQL=5.0.27
Oracle MySQL=5.0.33
Oracle MySQL=5.0.37
Oracle MySQL=5.0.41
Oracle MySQL=5.0.45
Oracle MySQL=5.0.67
Oracle MySQL=5.0.75
Oracle MySQL=5.0.77
Oracle MySQL=5.0.81
Oracle MySQL=5.1.30
Oracle MySQL=5.1.33
Oracle MySQL=5.1.35
Oracle MySQL=5.1.36
Oracle MySQL=5.1.38
Oracle MySQL=5.0.83
Oracle MySQL=5.0.85
Oracle MySQL=5.0.86
Oracle MySQL=5.0.88
Oracle MySQL=5.0.89
Oracle MySQL=5.0.90
Oracle MySQL=5.0.91
Remediation
Patch Available
Event History
May 21, 2010
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Data Sourced
via NVD·05:30 PM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2010-1626?
CVE-2010-1626 has been classified with a medium severity due to its potential for data loss through a symlink attack.
2
How do I fix CVE-2010-1626?
To fix CVE-2010-1626, upgrade your MySQL installation to version 5.1.46 or later.
3
Who is affected by CVE-2010-1626?
CVE-2010-1626 affects users of MySQL version 5.1.45 and earlier, as well as several 5.0 versions.
4
What impact does CVE-2010-1626 have on MySQL users?
CVE-2010-1626 can allow local users to delete another user's MyISAM table data and index files, leading to potential data loss.
5
Is CVE-2010-1626 a remote or local vulnerability?
CVE-2010-1626 is a local vulnerability, requiring access to the MySQL server to exploit.