CVE-2017-5146
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware Version A17. Sensitive information is stored in clear-text.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCarlo Gavazzi VMU-C EM and VMU-C PV devices store sensitive information (likely credentials, configuration data, or authentication tokens) in clear-text format without encryption. This allows attackers who gain any level of access to the device or its storage to retrieve sensitive data in plaintext, potentially leading to unauthorized access or further exploitation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device web interface, SNMP interface, or check device labeling/documentation to confirm the target is a Carlo Gavazzi VMU-C EM or VMU-C PV deviceAffected if Device is a Carlo Gavazzi VMU-C EM or VMU-C PV unit
-
Determine firmware versionRetrieve the installed firmware version from the device web interface, SNMP OID, or device status page via serial connectionAffected if Any firmware version is present on VMU-C EM or VMU-C PV (all versions are affected)
-
Check for stored credentials or tokensExamine device configuration pages, backup files, or storage for user accounts, API keys, authentication tokens, or network credentials stored without encryptionAffected if Credentials, tokens, or authentication data are stored on the device in plaintext
-
Assess network exposureReview firewall rules, access control lists, or network topology to determine if the device is directly accessible from untrusted networks or the internetAffected if Device is exposed to untrusted networks without proper network segmentation or access controls
If the device is a Carlo Gavazzi VMU-C EM or VMU-C PV with any firmware version, it stores sensitive data without encryption and could be affected if attackers gain any access to the device or its storage.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate VMU-C EM firmware to version A11_U05 or later, and VMU-C PV firmware to version A17 or later. Prior to update, ensure devices are not exposed to untrusted networks and conduct during a planned maintenance window.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-5146 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data