Is CVE-2017-3290 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2017-3290 being exploited in the wild.

How severe is CVE-2017-3290?

High severity, with a CVSS score of 7.9, published 27 January 2017.

Which products and versions are affected?

Oracle VirtualBox prior to 5.0.32, prior to 5.1.14.

Is there a fix for CVE-2017-3290?

A patch was published on 2017-01-17: Oracle Critical Patch Update (CPU) released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2017-3290 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2017-3290?

Check whether you run Oracle VirtualBox at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2017-3290: Oracle VM VirtualBox integrity and DoS vulnerability in Shared Folder

CVE-2017-3290 · Severity: high · CVSS 7.9 · Published 2017-01-27

A vulnerability in Oracle VM VirtualBox's Shared Folder feature allows a high-privileged user on a guest system to compromise the virtualization software. This can lead to the unauthorized modification or deletion of critical data and can be used to crash the virtual machine environment entirely. Such an exploit could disrupt business operations and impact the integrity of data stored within the virtualized infrastructure.

Technologies: Oracle VirtualBox. Vendors: Oracle.

Quick answers

Is CVE-2017-3290 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3290 being exploited in the wild.
How severe is CVE-2017-3290?: High severity, with a CVSS score of 7.9, published 27 January 2017.
Which products and versions are affected?: Oracle VirtualBox prior to 5.0.32, prior to 5.1.14.
Is there a fix for CVE-2017-3290?: A patch was published on 2017-01-17: Oracle Critical Patch Update (CPU) released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-3290 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2017-3290?: Check whether you run Oracle VirtualBox at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability exists in the Shared Folder subcomponent of Oracle VM VirtualBox (versions prior to 5.0.32 and 5.1.14). The flaw is categorized as 'easily exploitable' and requires a high-privileged attacker with local logon access to the infrastructure where VirtualBox executes. Successful exploitation allows an attacker to perform unauthorized creation, deletion, or modification of critical data or all accessible data within VirtualBox. Additionally, the attacker can cause a persistent hang or repeatable crash, resulting in a complete denial of service. The vulnerability is notable for its 'Scope' impact (S:C), meaning an exploit in VirtualBox can impact the underlying host or other products.

Affected products

Oracle VM VirtualBox prior to 5.0.32, prior to 5.1.14

Timeline

2017-01-27: advisory: Initial NVD publication
2017-01-17: patched: Oracle Critical Patch Update (CPU) released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.