dbcve.org
Vmu C Em FirmwareOperating system · Carlosgavazzi

CVE-2017-5144

CRITICAL · 9.8 CVSS v3.0 Published 2017-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware Version A17. The access control flaw allows access to most application functions without authentication.

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 · high confidence

The Carlo Gavazzi VMU-C EM and VMU-C PV energy monitoring devices contain an authentication bypass vulnerability in firmware versions prior to A11_U05 and A17 respectively. The access control flaw allows unauthenticated access to most application functions, enabling remote attackers to interact with the device without credentials.

MitigationUpdate firmware to version A11_U05 (for VMU-C EM) or version A17 (for VMU-C PV) or later to remediate this authentication bypass. If updating is not immediately possible, network isolation and restricting external access to the device management interface should be implemented as compensating controls.

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 data
Vmu C Em FirmwareOperating system
Affected:all versions
Vmu C Pv FirmwareOperating system
Affected:all versions

CVSS 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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Carlo Gavazzi device model
    Locate the device nameplate, management interface, or web console to confirm whether the unit is a VMU-C EM or VMU-C PV energy monitor
    Affected if The device is a Carlo Gavazzi VMU-C EM or VMU-C PV unit
  2. Determine the installed firmware version
    Access the device web interface, serial console, or management software and locate the firmware version information typically displayed in system status or about sections
    Affected if The firmware version cannot be confirmed or is displayed as a version number below the fixed releases
  3. Compare firmware version to the fixed releases
    For VMU-C EM units, check if firmware version is prior to A11_U05. For VMU-C PV units, check if firmware version is prior to A17
    Affected if The installed firmware version is below A11_U05 (for VMU-C EM) or below A17 (for VMU-C PV)
  4. Test unauthenticated access to application functions
    Attempt to access device application endpoints, configuration pages, or control functions without providing credentials
    Affected if Application functions are accessible without authentication

A user is affected if their VMU-C EM firmware is below A11_U05 or their VMU-C PV firmware is below A17, or if the device allows unauthenticated access to application functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update firmware to version A11_U05 (for VMU-C EM) or version A17 (for VMU-C PV) or later to remediate this authentication bypass. If updating is not immediately possible, network isolation and restricting external access to the device management interface should be implemented as compensating controls.

Recommended fix High confidence

VMU-C EM: A11_U05 or later; VMU-C PV: A17 or later

  1. Identify the specific Carlo Gavazzi VMU-C device model (EM or PV) in your environment
  2. Check the current firmware version of the device
  3. For VMU-C EM devices: Upgrade firmware to Version A11_U05 or later
  4. For VMU-C PV devices: Upgrade firmware to Version A17 or later
  5. After upgrading, verify that authentication is now required to access application functions
  6. Confirm the upgrade was successful by checking the firmware version reported by the device

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vmu C Em Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5144 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5144 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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