CVE-2006-1516: Medium severity mysql mysql vulnerability

Published May 5, 2006
·
Updated

The checkconnection function in sqlparse.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.

Affected Software

71 affected components
MySQL mysql=4.1.0
MySQL mysql=4.1.3
MySQL mysql=4.1.8
MySQL mysql=4.1.10
MySQL mysql=4.1.12
MySQL mysql=4.1.13
MySQL mysql=4.1.14
MySQL mysql=4.1.15
MySQL mysql=5.0.1
MySQL mysql=5.0.2
MySQL mysql=5.0.3
MySQL mysql=5.0.4
MySQL mysql=5.0.5
MySQL mysql=5.0.10
MySQL mysql=5.0.15
MySQL mysql=5.0.16
MySQL mysql=5.0.17
Oracle MySQL=4.0.0
Oracle MySQL=4.0.1
Oracle MySQL=4.0.2
Oracle MySQL=4.0.3
Oracle MySQL=4.0.4
Oracle MySQL=4.0.5
Oracle MySQL=4.0.5a
Oracle MySQL=4.0.6
Oracle MySQL=4.0.7
Oracle MySQL=4.0.7-gamma
Oracle MySQL=4.0.8
Oracle MySQL=4.0.8-gamma
Oracle MySQL=4.0.9
Oracle MySQL=4.0.9-gamma
Oracle MySQL=4.0.10
Oracle MySQL=4.0.11
Oracle MySQL=4.0.11-gamma
Oracle MySQL=4.0.12
Oracle MySQL=4.0.13
Oracle MySQL=4.0.14
Oracle MySQL=4.0.15
Oracle MySQL=4.0.16
Oracle MySQL=4.0.17
Oracle MySQL=4.0.18
Oracle MySQL=4.0.19
Oracle MySQL=4.0.20
Oracle MySQL=4.0.21
Oracle MySQL=4.0.23
Oracle MySQL=4.0.24
Oracle MySQL=4.0.25
Oracle MySQL=4.0.26
Oracle MySQL=4.1.0-alpha
Oracle MySQL=4.1.2-alpha
Oracle MySQL=4.1.3-beta
Oracle MySQL=4.1.4
Oracle MySQL=4.1.5
Oracle MySQL=4.1.6
Oracle MySQL=4.1.7
Oracle MySQL=4.1.9
Oracle MySQL=4.1.11
Oracle MySQL=4.1.16
Oracle MySQL=4.1.17
Oracle MySQL=4.1.18
Oracle MySQL=5.0.0-alpha
Oracle MySQL=5.0.3-beta
Oracle MySQL=5.0.6
Oracle MySQL=5.0.7
Oracle MySQL=5.0.8
Oracle MySQL=5.0.9
Oracle MySQL=5.0.11
Oracle MySQL=5.0.12
Oracle MySQL=5.0.13
Oracle MySQL=5.0.14
Oracle MySQL=5.0.18

Event History

May 5, 2006
CVE Published
12:46 PM
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2006-1516?

CVE-2006-1516 is considered a moderate severity vulnerability due to its potential to allow remote attackers to read sensitive memory contents.

2

How do I fix CVE-2006-1516?

To fix CVE-2006-1516, it is recommended to upgrade to MySQL version 5.0.21 or later where the vulnerability has been addressed.

3

What versions of MySQL are affected by CVE-2006-1516?

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.

4

Can CVE-2006-1516 be exploited remotely?

Yes, CVE-2006-1516 can be exploited remotely by attackers sending specially crafted usernames to the affected MySQL servers.

5

What is the impact of exploiting CVE-2006-1516?

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203