CVE-2023-22098 is an easily exploitable vulnerability in the Core component of Oracle VM VirtualBox affecting 7.0.x releases prior to 7.0.12. Exploitation requires a high-privileged attacker with logon access to the infrastructure where VirtualBox executes. Successful exploitation can compromise Oracle VM VirtualBox and, because the issue has scope change, may significantly affect additional products or components beyond the vulnerable VirtualBox security boundary. Oracle rates the issue with CVSS 3.1 vector AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H, indicating low attack complexity, no user interaction requirement, and high impact to confidentiality, integrity, and availability.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (PoC) exploit for CVE-2023-22098, a VirtualBox guest-to-host escape vulnerability discovered in the virtio-net device implementation. The exploit is implemented as a Linux kernel module (exploit.c) and is built using the provided Makefile. The README.md provides background and credits, as well as a link to a detailed blog post. The main exploit logic is in exploit.c, which defines a custom virtio-net driver. The exploit leverages out-of-bounds writes in the virtio-net control queue to manipulate kernel memory, construct a ROP chain, and ultimately achieve code execution on the host from a guest VM. The exploit is highly targeted, requiring VirtualBox 7.0.10 r158379 and a guest using the virtio-net device. No network endpoints or external IPs are hardcoded; the exploit operates entirely within the context of the host and guest VM interaction via the virtio-net device. The repository structure is straightforward: - exploit.c: The main exploit code (Linux kernel module) - Makefile: For building the kernel module - README.md: Documentation and background This exploit is a PoC and demonstrates the vulnerability, but does not include a weaponized or easily customizable payload.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.