Oracle MySQL Server up to 8.0.13 Packaging access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.9$0-$5k0.00

Summaryinfo

A vulnerability was found in Oracle MySQL Server up to 8.0.13. It has been rated as problematic. This impacts an unknown function of the component Packaging. Performing a manipulation results in access control. This vulnerability was named CVE-2019-2536. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Oracle MySQL Server up to 8.0.13 (Database Software). It has been classified as problematic. This affects an unknown function of the component Packaging. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on availability.

The bug was discovered 01/15/2019. The weakness was presented 01/16/2019 with Oracle as Oracle Critical Patch Update Advisory - January 2019 as confirmed advisory (Website). The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2019-2536 since 12/14/2018. The exploitability is told to be difficult. An attack has to be approached locally. Additional levels of successful authentication are necessary for exploitation. It demands that the victim is doing some kind of user interaction. 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 121229 (MySQL 8.0.x < 8.0.14 Multiple Vulnerabilities (Jan 2019 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 20103 (Oracle MySQL January 2019 Critical Patch Update (CPUJAN2019)).

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 (121229) and SecurityFocus (BID 106622†). See VDB-125486, VDB-129551, VDB-129543 and VDB-129544 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.9

VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score (Oracle): 5.0
Vendor Vector (Oracle): 🔍

NVD Base Score: 5.0
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 121229
Nessus Name: MySQL 8.0.x < 8.0.14 Multiple Vulnerabilities (Jan 2019 CPU)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

12/14/2018 🔍
01/15/2019 +32 days 🔍
01/15/2019 +0 days 🔍
01/16/2019 +0 days 🔍
01/16/2019 +0 days 🔍
01/16/2019 +0 days 🔍
01/16/2019 +0 days 🔍
01/17/2019 +1 days 🔍
06/29/2024 +1990 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: Oracle Critical Patch Update Advisory - January 2019
Organization: Oracle
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2019-2536 (🔍)
GCVE (CVE): GCVE-0-2019-2536
GCVE (VulDB): GCVE-100-129633
SecurityFocus: 106622 - Oracle MySQL Server Multiple Local Security Vulnerabilities

See also: 🔍

Entryinfo

Created: 01/16/2019 11:14
Updated: 06/29/2024 16:19
Changes: 01/16/2019 11:14 (81), 04/30/2020 17:21 (6), 06/28/2023 10:24 (4), 06/29/2024 16:19 (16)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!