First published: Fri May 05 2006(Updated: )
The check_connection function in sql_parse.cc in MySQL 4.0.x up to 4.0.26, 4.1.x up to 4.1.18, and 5.0.x up to 5.0.20 allows remote attackers to read portions of memory via a username without a trailing null byte, which causes a buffer over-read.
Credit: security@debian.org
Affected Software | Affected Version | How to fix |
---|---|---|
MySQL Server | =4.1.0 | |
MySQL Server | =4.1.3 | |
MySQL Server | =4.1.8 | |
MySQL Server | =4.1.10 | |
MySQL Server | =4.1.12 | |
MySQL Server | =4.1.13 | |
MySQL Server | =4.1.14 | |
MySQL Server | =4.1.15 | |
MySQL Server | =5.0.1 | |
MySQL Server | =5.0.2 | |
MySQL Server | =5.0.3 | |
MySQL Server | =5.0.4 | |
MySQL Server | =5.0.5 | |
MySQL Server | =5.0.10 | |
MySQL Server | =5.0.15 | |
MySQL Server | =5.0.16 | |
MySQL Server | =5.0.17 | |
MySQL | =4.0.0 | |
MySQL | =4.0.1 | |
MySQL | =4.0.2 | |
MySQL | =4.0.3 | |
MySQL | =4.0.4 | |
MySQL | =4.0.5 | |
MySQL | =4.0.5a | |
MySQL | =4.0.6 | |
MySQL | =4.0.7 | |
MySQL | =4.0.7-gamma | |
MySQL | =4.0.8 | |
MySQL | =4.0.8-gamma | |
MySQL | =4.0.9 | |
MySQL | =4.0.9-gamma | |
MySQL | =4.0.10 | |
MySQL | =4.0.11 | |
MySQL | =4.0.11-gamma | |
MySQL | =4.0.12 | |
MySQL | =4.0.13 | |
MySQL | =4.0.14 | |
MySQL | =4.0.15 | |
MySQL | =4.0.16 | |
MySQL | =4.0.17 | |
MySQL | =4.0.18 | |
MySQL | =4.0.19 | |
MySQL | =4.0.20 | |
MySQL | =4.0.21 | |
MySQL | =4.0.23 | |
MySQL | =4.0.24 | |
MySQL | =4.0.25 | |
MySQL | =4.0.26 | |
MySQL | =4.1.0-alpha | |
MySQL | =4.1.2-alpha | |
MySQL | =4.1.3-beta | |
MySQL | =4.1.4 | |
MySQL | =4.1.5 | |
MySQL | =4.1.6 | |
MySQL | =4.1.7 | |
MySQL | =4.1.9 | |
MySQL | =4.1.11 | |
MySQL | =4.1.16 | |
MySQL | =4.1.17 | |
MySQL | =4.1.18 | |
MySQL | =5.0.0-alpha | |
MySQL | =5.0.3-beta | |
MySQL | =5.0.6 | |
MySQL | =5.0.7 | |
MySQL | =5.0.8 | |
MySQL | =5.0.9 | |
MySQL | =5.0.11 | |
MySQL | =5.0.12 | |
MySQL | =5.0.13 | |
MySQL | =5.0.14 | |
MySQL | =5.0.18 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2006-1516 is considered a moderate severity vulnerability due to its potential to allow remote attackers to read sensitive memory contents.
To fix CVE-2006-1516, it is recommended to upgrade to MySQL version 5.0.21 or later where the vulnerability has been addressed.
CVE-2006-1516 affects MySQL versions 4.0.x up to 4.0.26, 4.1.x up to 4.1.18, and 5.0.x up to 5.0.20.
Yes, CVE-2006-1516 can be exploited remotely by attackers sending specially crafted usernames to the affected MySQL servers.
Exploiting CVE-2006-1516 can lead to unauthorized access to sensitive data from the server's memory, potentially exposing user credentials or other sensitive information.