cPanel up to 82.0.1 MySQL Password credentials management

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.
5.5$0-$5k0.00

Summaryinfo

A vulnerability was found in cPanel up to 82.0.1. It has been classified as problematic. Affected by this issue is some unknown functionality of the component MySQL. This manipulation causes credentials management (Password). This vulnerability is tracked as CVE-2019-14389. The attack is restricted to local execution. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic was found in cPanel up to 82.0.1 (Hosting Control Software). Affected by this vulnerability is an unknown code block of the component MySQL. The manipulation with an unknown input leads to a credentials management vulnerability (Password). The CWE definition for the vulnerability is CWE-255. As an impact it is known to affect confidentiality. The summary by CVE is:

cPanel before 82.0.2 allows local users to discover the MySQL root password (SEC-510).

The weakness was disclosed 07/30/2019. This vulnerability is known as CVE-2019-14389 since 07/29/2019. An attack has to be approached locally. The requirement for exploitation is a single authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

Upgrading to version 82.0.2 eliminates this vulnerability.

The entries VDB-139001, VDB-139000, VDB-138999 and VDB-138998 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Name: Password
Class: Credentials management / Password
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: cPanel 82.0.2

Timelineinfo

07/29/2019 🔍
07/30/2019 +1 days 🔍
07/31/2019 +1 days 🔍
11/14/2023 +1567 days 🔍

Sourcesinfo

Advisory: documentation.cpanel.net
Status: Not defined

CVE: CVE-2019-14389 (🔍)
GCVE (CVE): GCVE-0-2019-14389
GCVE (VulDB): GCVE-100-138997
See also: 🔍

Entryinfo

Created: 07/31/2019 08:59
Updated: 11/14/2023 09:42
Changes: 07/31/2019 08:59 (38), 07/16/2020 06:44 (18), 11/14/2023 09:42 (4)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!