CVE-2017-5146 is an information exposure vulnerability in Carlo Gavazzi VMU-C EM (prior to firmware A11_U05) and VMU-C PV (prior to firmware A17) devices, where sensitive information is stored in clear text. This allows an attacker with access to the device or its storage to retrieve sensitive data without needing to bypass encryption or other protection mechanisms.
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 auxiliary scanner module targeting Carlo Gavazzi Energy Meters (VMU-C EM and VMU-C PV) vulnerable to CVE-2017-5146. The module performs several actions: it first verifies if the target is a Carlo Gavazzi device by checking the web portal, then attempts to brute-force login credentials using provided or default username/password pairs. Upon successful authentication, it extracts the firmware version and attempts to retrieve the SMTP configuration, including credentials (if the user has admin privileges). Additionally, the module exploits an access control vulnerability to download the EWplant.db database file without authentication, which contains sensitive plant data. The module is written in Ruby and is designed to be used within the Metasploit framework. All HTTP endpoints used for exploitation are clearly defined in the code.
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.