Loading vulnerability…
CVE-2019-0888 is a remote code execution vulnerability in Microsoft ActiveX Data Objects (ADO) due to improper handling of objects in memory. An attacker can exploit this by convincing a user to visit a malicious website, which can trigger the vulnerability and allow execution of arbitrary code with the privileges of the victim user. The vulnerability is addressed by modifying how ADO handles objects in memory to prevent exploitation.
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-2019-0888, a use-after-free vulnerability in Windows ActiveX Data Objects (ADO) when used via VBScript in Internet Explorer. The repository consists of a README.md with a brief description and a single HTML file (cve-2019-0888-poc.html) containing the exploit code. The exploit works by creating multiple ADO Recordset objects and connecting to a local SQL Server Express instance (SQLEXPRESS). Through a series of VBScript manipulations, it triggers a use-after-free condition, then leverages type confusion and memory manipulation to leak the base address of the loaded vbscript.dll module. The PoC demonstrates the vulnerability and the ability to read memory, but does not provide a weaponized payload or remote code execution. The attack vector is via a browser (Internet Explorer) and requires the target to have a local SQL Server Express instance accessible. The main fingerprintable endpoint is the local database connection string targeting .\SQLEXPRESS.
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.