Loading vulnerability…
H2 Database Engine 1.4.197, including deployments such as Datomic before 0.9.5697 that embed or use H2, is vulnerable to remote code execution because the SQL CREATE ALIAS feature can be used to execute arbitrary Java code. An attacker able to submit crafted SQL statements to the H2 instance can define an alias backed by attacker-controlled Java and cause that code to run in the context of the H2 process. The vendor noted that H2 is not designed to be run outside of a secure environment.
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 single Metasploit module (modules/exploits/linux/http/h2_webinterface_rce.rb) that exploits a remote code execution vulnerability in the H2 database web interface (CVE-2018-10054). The exploit abuses the 'CREATE ALIAS' SQL feature to define a Java function that executes arbitrary system commands. The module authenticates to the H2 web interface using provided credentials, creates a malicious alias, and uses it to download and execute a payload (typically a reverse shell) on the target system. The exploit is weaponized, allowing for customizable payloads and reliable exploitation. The module interacts with several HTTP endpoints of the H2 web interface, including /login.jsp, /login.do, and /query.do. The code is written in Ruby and is designed to be used within the Metasploit framework.
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.
3 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.