| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in MySQL up to 3.20.52 on Windows. It has been classified as critical. Impacted is an unknown function of the component Service Handler. Performing a manipulation results in privileges management. This vulnerability was named CVE-2002-1921. There is no available exploit.
Details
A vulnerability was found in MySQL up to 3.20.52 on Windows (Database Software). It has been classified as critical. This affects an unknown code block of the component Service Handler. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The default configuration of MySQL 3.20.32 through 3.23.52, when running on Windows, does set the bind address to the loopback interface, which allows remote attackers to connect to the database.
The weakness was presented 12/31/2002 by Mike (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2002-1921 since 06/29/2005. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 05/25/2019). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
The vulnerability scanner Nessus provides a plugin with the ID 17821 (MySQL 3.20.32 - 3.23.52 Weak Default Configuration), 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 19727 (MySQL Bind Address Not Enabled Weak Default Configuration Vulnerability).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (9908), Tenable (17821), SecurityFocus (BID 5511†) and Vulnerability Center (SBV-5771†). See VDB-19565 for similar entry. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
- 3.20.0
- 3.20.1
- 3.20.2
- 3.20.3
- 3.20.4
- 3.20.5
- 3.20.6
- 3.20.7
- 3.20.8
- 3.20.9
- 3.20.10
- 3.20.11
- 3.20.12
- 3.20.13
- 3.20.14
- 3.20.15
- 3.20.16
- 3.20.17
- 3.20.18
- 3.20.19
- 3.20.20
- 3.20.21
- 3.20.22
- 3.20.23
- 3.20.24
- 3.20.25
- 3.20.26
- 3.20.27
- 3.20.28
- 3.20.29
- 3.20.30
- 3.20.31
- 3.20.32
- 3.20.33
- 3.20.34
- 3.20.35
- 3.20.36
- 3.20.37
- 3.20.38
- 3.20.39
- 3.20.40
- 3.20.41
- 3.20.42
- 3.20.43
- 3.20.44
- 3.20.45
- 3.20.46
- 3.20.47
- 3.20.48
- 3.20.49
- 3.20.50
- 3.20.51
- 3.20.52
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 17821
Nessus Name: MySQL 3.20.32 - 3.23.52 Weak Default Configuration
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/18/2002 🔍08/19/2002 🔍
12/31/2002 🔍
12/31/2002 🔍
11/14/2004 🔍
06/29/2005 🔍
01/18/2012 🔍
08/05/2014 🔍
05/25/2019 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Mike
Status: Not defined
CVE: CVE-2002-1921 (🔍)
GCVE (CVE): GCVE-0-2002-1921
GCVE (VulDB): GCVE-100-19563
X-Force: 9908
SecurityFocus: 5511 - MySQL Bind Address Not Enabled Weak Default Configuration Vulnerability
Vulnerability Center: 5771 - MySQL has Default Root Password, Critical
See also: 🔍
Entry
Created: 08/05/2014 10:56Updated: 05/25/2019 18:37
Changes: 08/05/2014 10:56 (67), 05/25/2019 18:37 (2)
Complete: 🔍
Cache ID: 216:844:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.