Loading vulnerability…
AMCS Group Trux Waste Management Software prior to version 7.19.0018.26912 contains a vulnerability where a static, hard-coded AES Key-IV pair is present in the TxUtilities.dll and TruxUser.cfg components. This allows local attackers to retrieve the key material and decrypt sensitive data protected by these components, leading to potential exposure of confidential information.
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 (PoC) exploit for CVE-2024-22734, a vulnerability in AMCS Trux software (version 7.19.0018). The exploit is implemented in C# and consists primarily of the 'Program.cs' file, which demonstrates how to extract and decrypt the master database credentials from a local installation of the vulnerable software. The exploit works by loading the 'TxUtilities.dll' file to access hard-coded AES keys and IVs, then reading the encrypted credentials from the 'TruxUser.cfg' configuration file. Using these static keys, the exploit decrypts the credentials and outputs the database username and password. The attack requires local access to the target system and access to the relevant DLL and configuration files. The repository is structured as a standard Visual Studio C# project, with supporting files for project configuration and metadata. No network endpoints are involved; the attack is purely local and targets file-based secrets.
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.