Loading vulnerability…
CVE-2021-42392 is a remote code execution vulnerability in H2 Database arising from unsafe handling of attacker-controlled driver class names and database URLs by org.h2.util.JdbcUtils.getConnection. The vulnerable code accepts a driver class name and connection URL and can be induced to use a JNDI driver name together with an LDAP or RMI-backed endpoint. This allows untrusted input to influence how the connection is resolved, leading to remote loading or execution of attacker-controlled code. The issue is particularly significant when exposed through the H2 Console, where it can result in unauthenticated remote code execution.
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 is a Proof-of-Concept (PoC) exploit for CVE-2021-42392, a critical remote code execution vulnerability in H2 Database versions prior to 2.0.206. The exploit leverages the CREATE ALIAS feature to execute arbitrary system commands on the server via a crafted SQL/Java payload. The repository provides a Docker-based lab environment with two main services: a vulnerable H2 Database server (running on port 9092) and a client container with a Python script (h2_exploit.py) that automates the exploitation process. The exploit script connects to the H2 server using JDBC, creates a malicious ALIAS, and triggers command execution. The setup requires the H2 TCP service to be exposed, valid database credentials, and the presence of the Java compiler on the server. The repository is structured for ease of testing and educational demonstration, with clear instructions and minimal dependencies.
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.
1 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.