CVE-2024-56428 affects itech iLabClient 3.7.1. The product stores server credentials in cleartext within the local iLabClient database, specifically in the CONFIGS table. A local attacker who can access the client-side database can read these credentials directly without needing to defeat encryption or other protection mechanisms. The vulnerability is therefore a client-side sensitive-data exposure issue caused by insecure storage of authentication material.
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 provides a proof-of-concept exploit for CVE-2024-56428, a vulnerability in the iLabClient software by Lufthansa Industry Solutions. The vulnerability is the storage of cleartext credentials in a local Apache Derby database. The repository contains a Bash script (get_configs.sh) that automates the process of extracting these credentials by invoking the Apache Derby 'ij' tool via Java to run a provided SQL script (script_sql.sql). The SQL script connects to the local Derby database (default path: C:\ilabClient\db\iLabClient) and extracts the configuration data, including passwords, from the 'configs' table. The exploit requires local access to the target system and the ability to run the Java and Derby tools provided with the iLabClient installation. The repository is structured with a README explaining the vulnerability and usage, the Bash script for automation, the SQL script for data extraction, and a .gitignore file. No network or remote attack vector is present; the exploit is purely local and targets the file system and local database.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.