Skip to content
Fencer Intel
high 7.9

CVE-2017-3575 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-12695

cvss
7.9
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits
1
Exploit-DB

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. Easily "exploitable" 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 creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle VM VirtualBox. CVSS 3.0 Base Score 7.9 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H).

Patch / fix

  • Oracle Corporation Oracle VM VirtualBox 5.0.38, 5.1.20

Timeline

  1. First public exploit (EDB-41906)
  2. Published

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

1.44% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-41906 Oracle VM VirtualBox - 'virtio-net' Guest-to-Host Out-of-Bounds Write dos, 2017-04-20

CVSS scores

assigned by version score vector
NVD 3.0 7.9 CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H
NVD 2.0 3.6 AV:L/AC:L/Au:N/C:N/I:P/A:P

Affected products

  • Oracle Corporation Oracle VM VirtualBox

References

Sources

Fencer Intel 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.