Oracle MySQL Server up to 5.6.41/5.7.23/8.0.12 InnoDB access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Oracle MySQL Server up to 5.6.41/5.7.23/8.0.12. Impacted is an unknown function of the component InnoDB. The manipulation leads to access control. This vulnerability is uniquely identified as CVE-2018-3143. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Oracle MySQL Server up to 5.6.41/5.7.23/8.0.12 (Database Software) and classified as critical. This issue affects some unknown processing of the component InnoDB. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is availability.
The bug was discovered 10/16/2018. The weakness was disclosed 10/16/2018 with Oracle as Oracle Critical Patch Update Advisory - October 2018 as confirmed advisory (Website). The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2018-3143 since 12/15/2017. The attack may be initiated remotely. Required for exploitation is a simple authentication. 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 118234 (MySQL 5.6.x < 5.6.42 Multiple Vulnerabilities (October 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 r. The commercial vulnerability scanner Qualys is able to test this issue with plugin 197284 (Ubuntu Security Notification for Mysql-5.5, Mysql-5.7 Vulnerabilities (USN-3799-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 (118234) and SecurityFocus (BID 105600†). The entries VDB-90449, VDB-91385, VDB-91680 and VDB-91681 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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.6.39
- 5.6.40
- 5.6.41
- 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
- 5.7.21
- 5.7.22
- 5.7.23
- 8.0.0
- 8.0.1
- 8.0.2
- 8.0.3
- 8.0.4
- 8.0.5
- 8.0.6
- 8.0.7
- 8.0.8
- 8.0.9
- 8.0.10
- 8.0.11
- 8.0.12
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: 118234
Nessus Name: MySQL 5.6.x < 5.6.42 Multiple Vulnerabilities (October 2018 CPU)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
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 🔍10/16/2018 🔍
10/16/2018 🔍
10/16/2018 🔍
10/16/2018 🔍
10/16/2018 🔍
10/17/2018 🔍
10/19/2018 🔍
05/26/2023 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - October 2018
Organization: Oracle
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-3143 (🔍)
GCVE (CVE): GCVE-0-2018-3143
GCVE (VulDB): GCVE-100-125537
OVAL: 🔍
SecurityFocus: 105600 - Oracle MySQL Server Multiple Security Vulnerabilities
SecurityTracker: 1041888
See also: 🔍
Entry
Created: 10/17/2018 08:40Updated: 05/26/2023 17:07
Changes: 10/17/2018 08:40 (84), 04/03/2020 18:22 (6), 05/26/2023 17:07 (5)
Complete: 🔍
Cache ID: 216:C4E:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.