Loading vulnerability…
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core) affecting versions prior to 5.0.38 and prior to 5.1.20. The issue is described as easily exploitable by an unauthenticated attacker with logon to the infrastructure where VirtualBox executes, allowing compromise of VirtualBox. Successful exploitation can cause a hang or frequently repeatable crash (complete DoS) of VirtualBox and can also result in unauthorized update/insert/delete access to some VirtualBox-accessible data and unauthorized read access to a subset of VirtualBox-accessible data. CVSS v3.0: 8.5 (AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:H).
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.