CVE-2006-1517: Medium severity mysql mysql vulnerability

Published May 5, 2006
·
Updated

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 obtain sensitive information via a COMTABLEDUMP request with an incorrect packet length, which includes portions of memory in an error message.

Affected Software

71 affected components
MySQL mysql=5.0.5
MySQL mysql=5.0.10
MySQL mysql=5.0.15
MySQL mysql=5.0.17
MySQL mysql=4.1.13
MySQL mysql=5.0.3
MySQL mysql=4.1.15
MySQL mysql=4.1.8
MySQL mysql=4.1.14
MySQL mysql=4.1.12
MySQL mysql=4.1.10
MySQL mysql=5.0.2
MySQL mysql=5.0.1
MySQL mysql=4.1.0
MySQL mysql=5.0.4
MySQL mysql=4.1.3
MySQL mysql=5.0.16
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-gamma
Oracle MySQL=4.0.8
Oracle MySQL=4.0.9
Oracle MySQL=4.0.9-gamma
Oracle MySQL=4.0.10
Oracle MySQL=4.0.11-gamma
Oracle MySQL=4.0.11
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.11
Oracle MySQL=5.0.12
Oracle MySQL=5.0.13
Oracle MySQL=5.0.14
Oracle MySQL=5.0.18
Oracle MySQL=5.0.7
Oracle MySQL=5.0.8
Oracle MySQL=5.0.9

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-1517?

CVE-2006-1517 is considered a moderate severity vulnerability due to its ability to expose sensitive information.

2

How do I fix CVE-2006-1517?

The remediation for CVE-2006-1517 is to upgrade MySQL to version 4.1.19 or later, or 5.0.21 or later.

3

What software versions are affected by CVE-2006-1517?

CVE-2006-1517 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-1517 be exploited remotely?

Yes, CVE-2006-1517 can be exploited remotely by attackers using a COM_TABLE_DUMP request.

5

What type of information can be leaked due to CVE-2006-1517?

CVE-2006-1517 can leak sensitive information contained in memory, such as portions of error messages.

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