CVE-2017-3513 json
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core).
published 2017-04-24 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-12634
- cvss
- 2.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). Supported versions that are affected are Prior to 5.0.38 and Prior to 5.1.20. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle VM VirtualBox accessible data. CVSS 3.0 Base Score 2.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N).
Patch / fix
- Oracle Corporation Oracle VM VirtualBox 5.0.38, 5.1.20
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 2.5 | CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N |
| NVD | 2.0 | 1.9 | AV:L/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- Oracle Corporation Oracle VM VirtualBox
References
-
oracle.com
/technetwork/security-advisory/cpuapr2017-3236618.html
patch, vendor-advisory
-
securitytracker.com
/id/1038288
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/97736
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-3513
- NVD CVE-2017-3513
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.