Oracle MySQL Server up to 5.6.38/5.7.20 InnoDB access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Oracle MySQL Server up to 5.6.38/5.7.20. This vulnerability affects unknown code of the component InnoDB. This manipulation causes access control. This vulnerability appears as CVE-2018-2612. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in Oracle MySQL Server up to 5.6.38/5.7.20 (Database Software). It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component InnoDB. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect integrity, and availability.
The bug was discovered 01/16/2018. The weakness was presented 01/18/2018 with Oracle as Oracle Critical Patch Update Advisory - January 2018 as confirmed advisory (Website). The advisory is shared at oracle.com. This vulnerability is known as CVE-2018-2612 since 12/15/2017. The exploitation appears to be easy. The attack can be launched remotely. A single authentication is required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 106102 (MySQL 5.7.x < 5.7.21 Multiple Vulnerabilities (RPM Check) (January 2018 CPU)), 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 l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176531 (Debian Security Update for mariadb-10.1 (DSA 4341-1)).
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (106102) and SecurityFocus (BID 102709†). See VDB-68431, VDB-89667, VDB-92931 and VDB-95678 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 5.6.0
- 5.6.1
- 5.6.2
- 5.6.3
- 5.6.4
- 5.6.5
- 5.6.6
- 5.6.7
- 5.6.8
- 5.6.9
- 5.6.10
- 5.6.11
- 5.6.12
- 5.6.13
- 5.6.14
- 5.6.15
- 5.6.16
- 5.6.17
- 5.6.18
- 5.6.19
- 5.6.20
- 5.6.21
- 5.6.22
- 5.6.23
- 5.6.24
- 5.6.25
- 5.6.26
- 5.6.27
- 5.6.28
- 5.6.29
- 5.6.30
- 5.6.31
- 5.6.32
- 5.6.33
- 5.6.34
- 5.6.35
- 5.6.36
- 5.6.37
- 5.6.38
- 5.7.0
- 5.7.1
- 5.7.2
- 5.7.3
- 5.7.4
- 5.7.5
- 5.7.6
- 5.7.7
- 5.7.8
- 5.7.9
- 5.7.10
- 5.7.11
- 5.7.12
- 5.7.13
- 5.7.14
- 5.7.15
- 5.7.16
- 5.7.17
- 5.7.18
- 5.7.19
- 5.7.20
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 6.5
Vendor Vector (Oracle): 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
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: Access controlCWE: CWE-284 / 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: 106102
Nessus Name: MySQL 5.7.x < 5.7.21 Multiple Vulnerabilities (RPM Check) (January 2018 CPU)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 53950
OpenVAS Name: Oracle Mysql Security Updates (jan2018-3236628) 03 - Windows
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
12/15/2017 🔍01/16/2018 🔍
01/16/2018 🔍
01/17/2018 🔍
01/17/2018 🔍
01/18/2018 🔍
01/18/2018 🔍
01/18/2018 🔍
01/31/2021 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - January 2018
Researcher: Oracle
Organization: Oracle
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-2612 (🔍)
GCVE (CVE): GCVE-0-2018-2612
GCVE (VulDB): GCVE-100-112093
OVAL: 🔍
SecurityFocus: 102709 - Oracle MySQL Server CVE-2018-2612 Remote Security Vulnerability
SecurityTracker: 1040216
See also: 🔍
Entry
Created: 01/18/2018 09:43Updated: 01/31/2021 16:04
Changes: 01/18/2018 09:43 (87), 12/24/2019 16:30 (4), 01/31/2021 15:59 (4), 01/31/2021 16:04 (1)
Complete: 🔍
Cache ID: 216::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.