| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Oracle MySQL Server up to 8.0.15. This affects an unknown function of the component InnoDB. This manipulation causes denial of service. The identification of this vulnerability is CVE-2019-2580. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic was found in Oracle MySQL Server up to 8.0.15 (Database Software). Affected by this vulnerability is an unknown code of the component InnoDB. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability.
The weakness was shared 04/16/2019 as Oracle Critical Patch Update Advisory - April 2019 as confirmed advisory (Website). The advisory is shared at oracle.com. This vulnerability is known as CVE-2019-2580. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 210323 (RHEL 7 : rh-mysql80-mysql (RHSA-2019:2484)), which helps to determine the existence of the flaw in a target environment. The commercial vulnerability scanner Qualys is able to test this issue with plugin 20109 (Oracle MySQL April 2019 Critical Patch Update (CPUAPR2019)).
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 (210323) and SecurityFocus (BID 107174†). The entries VDB-132588, VDB-132587, VDB-133580 and VDB-133572 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.9
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 4.9
Vendor Vector (Oracle): 🔍
NVD Base Score: 4.9
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: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: 210323
Nessus Name: RHEL 7 : rh-mysql80-mysql (RHSA-2019:2484)
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
12/14/2018 🔍04/16/2019 🔍
04/16/2019 🔍
04/18/2019 🔍
11/06/2024 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - April 2019
Status: Confirmed
CVE: CVE-2019-2580 (🔍)
GCVE (CVE): GCVE-0-2019-2580
GCVE (VulDB): GCVE-100-133669
SecurityFocus: 107174
See also: 🔍
Entry
Created: 04/18/2019 07:39Updated: 11/06/2024 02:12
Changes: 04/18/2019 07:39 (53), 09/03/2023 10:24 (7), 09/03/2023 10:29 (16), 11/06/2024 02:12 (16)
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.