Loading vulnerability…
DataEase is an open-source data visualization and analytics platform. Versions 2.10.20 and below contain a JDBC parameter blocklist bypass vulnerability in the MySQL datasource configuration. The Mysql class uses Lombok's @Data annotation, which auto-generates a public setter for the illegalParameters field that contains the JDBC security blocklist. When a datasource configuration is submitted as JSON, Jackson deserialization calls setIllegalParameters with an attacker-supplied empty list, replacing the blocklist before getJdbc() validation runs. This allows an authenticated attacker to include dangerous JDBC parameters such as allowLoadLocalInfile=true, and by pointing the datasource at a rogue MySQL server, exploit the LOAD DATA LOCAL INFILE protocol feature to read arbitrary files from the DataEase server filesystem, including sensitive environment variables and database credentials. This issue has been fixed in version 2.10.21.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository is a self-contained PoC and Docker lab for a four-stage exploit chain against DataEase <= v2.10.20, culminating in root RCE via Quartz deserialization. Structure is small and focused: docker-compose.yml plus conf/ and mysql/ stand up a vulnerable DataEase + MySQL environment; exploit/de_common.py provides reusable HTTP/API helpers for /dekey key recovery, RSA-encrypted login, JWT forgery, datasource creation, and previewSql invocation; exploit/de_rce_chain.py is the main end-to-end exploit that authenticates, registers a malicious datasource with illegalParameters=[] and allowMultiQueries=true, generates a CommonsCollections6 gadget using ysoserial in a Java 8 Docker container, and injects stacked SQL queries to overwrite Quartz JOB_DATA and trigger deserialization; exploit/file_read.py demonstrates the arbitrary file-read stage by coercing DataEase to connect to a rogue MySQL server; exploit/rogue_mysql.py implements that minimal rogue MySQL server and captures uploaded file contents via LOCAL INFILE. The exploit is operational rather than framework-based: it contains working payload generation and execution logic, supports arbitrary commands and reverse shells, and includes all infrastructure needed for local reproduction.
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.