Oracle VM VirtualBox up to 5.2.27/6.0.5 Core input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.7 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Oracle VM VirtualBox up to 5.2.27/6.0.5. This affects an unknown function of the component Core. Executing a manipulation can lead to an unknown weakness. This vulnerability appears as CVE-2019-2722. The attack requires local access. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical was found in Oracle VM VirtualBox up to 5.2.27/6.0.5 (Virtualization Software). This vulnerability affects an unknown code block of the component Core. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was presented 04/16/2019 as Oracle Critical Patch Update Advisory - April 2019 as confirmed advisory (Website). The advisory is shared for download at oracle.com. This vulnerability was named CVE-2019-2722. There are neither technical details nor an exploit publicly available.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 371750 (Oracle VM VirtualBox Multiple Vulnerabilities (CPUAPR2019)).
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
See VDB-133580, VDB-133572, VDB-133573 and VDB-133574 for similar entries. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 5.2.0
- 5.2.1
- 5.2.2
- 5.2.3
- 5.2.4
- 5.2.5
- 5.2.6
- 5.2.7
- 5.2.8
- 5.2.9
- 5.2.10
- 5.2.11
- 5.2.12
- 5.2.13
- 5.2.14
- 5.2.15
- 5.2.16
- 5.2.17
- 5.2.18
- 5.2.19
- 5.2.20
- 5.2.21
- 5.2.22
- 5.2.23
- 5.2.24
- 5.2.25
- 5.2.26
- 5.2.27
- 6.0.0
- 6.0.1
- 6.0.2
- 6.0.3
- 6.0.4
- 6.0.5
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.7
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 8.8
Vendor Vector (Oracle): 🔍
NVD Base Score: 8.8
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
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 🔍
09/04/2023 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - April 2019
Status: Confirmed
CVE: CVE-2019-2722 (🔍)
GCVE (CVE): GCVE-0-2019-2722
GCVE (VulDB): GCVE-100-133768
See also: 🔍
Entry
Created: 04/18/2019 07:39Updated: 09/04/2023 09:34
Changes: 04/18/2019 07:39 (51), 09/04/2023 09:31 (7), 09/04/2023 09:34 (18)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.