MySQL up to 5.1.11 Configuration File instance_options.cc complete_initialization numeric error ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in MySQL. Affected is the function instance_options::complete_initialization of the file instance_options.cc of the component Configuration File. Executing a manipulation can lead to numeric error.
This vulnerability appears as CVE-2006-3486. There is no available exploit.
The actual existence of this vulnerability is currently in question.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in MySQL (Database Software). It has been declared as problematic. This vulnerability affects the function instance_options::complete_initialization of the file instance_options.cc of the component Configuration File. The manipulation with an unknown input leads to a numeric error vulnerability. The CWE definition for the vulnerability is CWE-189. As an impact it is known to affect availability. CVE summarizes:
** DISPUTED ** Off-by-one buffer overflow in the Instance_options::complete_initialization function in instance_options.cc in the Instance Manager in MySQL before 5.0.23 and 5.1 before 5.1.12 might allow local users to cause a denial of service (application crash) via unspecified vectors, which triggers the overflow when the convert_dirname function is called. NOTE: the vendor has disputed this issue via e-mail to CVE, saying that it is only exploitable when the user has access to the configuration file or the Instance Manager daemon. Due to intended functionality, this level of access would already allow the user to disrupt program operation, so this does not cross security boundaries and is not a vulnerability.
The bug was discovered 07/04/2006. The weakness was presented 07/10/2006 (Website). The advisory is shared for download at vupen.com. This vulnerability was named CVE-2006-3486 since 07/10/2006. The exploitation appears to be easy. The attack needs to be approached locally. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $25k-$100k. The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 17831 (MySQL < 5.0.23 / 5.1.12 Denial of Service), 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.
Upgrading to version 5.0.23 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (27635), Tenable (17831), OSVDB (28288†) and Vulnerability Center (SBV-12268†). Once again VulDB remains the best source for vulnerability data.
Product
Type
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
- 5.0.20a
- 5.0.21
- 5.0.22
- 5.1.1
- 5.1.2
- 5.1.3
- 5.1.4
- 5.1.5
- 5.1.6
- 5.1.7
- 5.1.8
- 5.1.9
- 5.1.10
- 5.1.11
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 3.6
VulDB Base Score: 4.0
VulDB Temp Score: 3.6
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: Numeric errorCWE: CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 17831
Nessus Name: MySQL < 5.0.23 / 5.1.12 Denial of Service
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: MySQL 5.0.23
Timeline
07/04/2006 🔍07/10/2006 🔍
07/10/2006 🔍
07/10/2006 🔍
07/10/2006 🔍
07/13/2006 🔍
01/18/2012 🔍
03/12/2015 🔍
08/07/2024 🔍
Sources
Advisory: vupen.com⛔Status: Not defined
Disputed: 🔍
CVE: CVE-2006-3486 (🔍)
GCVE (CVE): GCVE-0-2006-3486
GCVE (VulDB): GCVE-100-31228
X-Force: 27635
OSVDB: 28288 - CVE-2006-3486 - MySQL - Buffer-overflow Issue
Vulnerability Center: 12268 - MySQL Instance Manager Off-By-One Buffer Overflow Local Denial of Service, Low
Vupen: ADV-2006-2700
Entry
Created: 03/12/2015 14:25Updated: 08/07/2024 23:10
Changes: 03/12/2015 14:25 (67), 06/22/2019 12:51 (3), 08/07/2024 23:10 (17)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.