| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Sun MySQL up to 5.0.20. This affects an unknown function of the component Authentication. This manipulation causes memory corruption. This vulnerability is tracked as CVE-2006-1516. Moreover, an exploit is present. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic was found in Sun MySQL up to 5.0.20 (Database Software). Affected by this vulnerability is some unknown processing of the component Authentication. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The bug was discovered 05/03/2006. The weakness was disclosed 05/03/2006 by Stefano Di Paola with isec (Website). The advisory is shared at dev.mysql.com. This vulnerability is known as CVE-2006-1516 since 03/30/2006. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available.
After even before and not, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 17697 (MySQL < 4.0.27 / 4.1.19 / 5.0.21 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Databases and running in the context r. The commercial vulnerability scanner Qualys is able to test this issue with plugin 117705 (CentOS Security Update for MySQL (CESA-2006:0544)).
Upgrading eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at dev.mysql.com. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published 2 months after the disclosure of the vulnerability. Attack attempts may be identified with Snort ID 16020. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 4620.
The vulnerability is also documented in the databases at X-Force (26236), Exploit-DB (1742), Tenable (17697), SecurityFocus (BID 17780†) and OSVDB (25226†). The entries VDB-2065, VDB-2196, VDB-2195 and VDB-30061 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 5.0.0
- 5.0.1
- 5.0.2
- 5.0.3
- 5.0.4
- 5.0.5
- 5.0.6
- 5.0.7
- 5.0.8
- 5.0.9
- 5.0.10
- 5.0.11
- 5.0.12
- 5.0.13
- 5.0.14
- 5.0.15
- 5.0.16
- 5.0.17
- 5.0.18
- 5.0.19
- 5.0.20
License
Support
- end of life (old version)
Website
- Vendor: https://www.oracle.com/sun/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 17697
Nessus Name: MySQL < 4.0.27 / 4.1.19 / 5.0.21 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 56788
OpenVAS Name: Debian Security Advisory DSA 1071-1 (mysql)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: dev.mysql.com
Snort ID: 16020
TippingPoint: 🔍
McAfee IPS: 🔍
McAfee IPS Version: 🔍
ISS Proventia IPS: 🔍
Fortigate IPS: 🔍
Timeline
03/30/2006 🔍05/02/2006 🔍
05/02/2006 🔍
05/02/2006 🔍
05/02/2006 🔍
05/03/2006 🔍
05/03/2006 🔍
05/03/2006 🔍
05/03/2006 🔍
05/05/2006 🔍
05/05/2006 🔍
05/07/2006 🔍
06/01/2006 🔍
11/18/2011 🔍
02/26/2025 🔍
Sources
Vendor: oracle.comAdvisory: dev.mysql.com
Researcher: Stefano Di Paola
Organization: isec
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2006-1516 (🔍)
GCVE (CVE): GCVE-0-2006-1516
GCVE (VulDB): GCVE-100-2197
OVAL: 🔍
X-Force: 26236
SecurityFocus: 17780 - MySQL Remote Information Disclosure and Buffer Overflow Vulnerabilities
Secunia: 19929 - MySQL Information Disclosure and Buffer Overflow Vulnerabilities, Less Critical
OSVDB: 25226 - MySQL Malformed Login Packet Remote Memory Disclosure
SecurityTracker: 1016017
Vulnerability Center: 11340 - MySQL Information Disclosure due to Input Validation Error of Login Packets, Medium
Vupen: ADV-2006-1633
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/05/2006 17:40Updated: 02/26/2025 06:59
Changes: 05/05/2006 17:40 (112), 06/17/2019 14:28 (1), 02/26/2025 06:59 (16)
Complete: 🔍
Cache ID: 216:609:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.