Loading vulnerability…
In Cachet versions prior to 2.5.1, authenticated users (regardless of privilege level) can access and leak sensitive configuration values from the dotenv file, including the application secret (APP_KEY) and various service passwords. The vulnerability is due to insufficient restrictions in the UpdateConfigCommandHandler, which allows exposure of nested variables in the dotenv configuration.
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 proof-of-concept exploit for CVE-2021-39174, targeting the Cachet status page application. The exploit is implemented in a single Python script ('exploit.py'), which automates the process of logging into a vulnerable Cachet instance, manipulating the mail configuration to inject references to sensitive environment variables, and then reading back the resolved values to extract secrets such as database credentials and application keys. The script requires valid user credentials and the URL of the target application. It uses the requests and BeautifulSoup libraries to interact with the web interface, and supports optional proxying. The README provides a brief description, and the LICENSE is GPLv3. The exploit demonstrates an information disclosure vulnerability and is suitable as a proof-of-concept for security testing.
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.