CVE-2019-2525 is an information disclosure vulnerability in the Core component of Oracle VM VirtualBox, affecting versions prior to 5.2.24 and 6.0.2. A low privileged attacker with local access to the infrastructure running VirtualBox can exploit this flaw to gain unauthorized access to critical or all data accessible by VirtualBox. The vulnerability is difficult to exploit due to high attack complexity and requires local access with low privileges.
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 working exploit for Oracle VirtualBox 6.0.0 (and likely other 6.x versions) that leverages two vulnerabilities: CVE-2019-2525 (information disclosure via crUnpackExtendGetAttribLocation) and CVE-2019-2548 (heap overflow via crServerDispatchReadPixels). The exploit is implemented in Python and is structured as follows: - `exploit.py`: The main exploit script, orchestrating the attack steps: memory leak, heap spray, heap corruption, and ultimately function pointer overwrite to achieve code execution on the host. - `lib/chromium.py`: Contains helper functions and constants for crafting Chromium/OpenGL messages and interacting with the VirtualBox 3D acceleration service. - `lib/hgcm.py`: Implements the low-level communication with the VirtualBox Host-Guest Communication Manager (HGCM) via device files (`/dev/vboxuser` on Linux, `\\.\VBoxGuest` on Windows). - `lib/opcodes.py`: Defines OpenGL/Chromium opcode constants used in message crafting. - `README.md`: Provides a detailed technical write-up (in Korean) explaining the vulnerabilities, exploitation steps, and includes a demo video link. - `vbox_bulid`: Reference to a VirtualBox builder Docker repository for setting up a test environment. The exploit works by leaking host memory addresses, performing a heap spray to control memory layout, exploiting a heap overflow to corrupt function pointers, and finally triggering execution of an arbitrary command ('xcalc') on the host, thus escaping the VM. The attack vector is local (from guest to host), requiring the attacker to have code execution in a VirtualBox guest with 3D acceleration enabled. The endpoints involved are the HGCM service 'VBoxSharedCrOpenGL' and the device files used for host-guest communication. The exploit is operational and demonstrates a full VM escape with arbitrary code execution on the host.
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.