CVE-2017-5145: An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to fir

This month

CRITICAL 10.0REMOTEMITIGATEMITIGATE

CVE-2017-5145 is a critical-severity flaw (CVSS 10.0) affecting vmu-c em firmware, vmu-c pv firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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. Successful exploitation of this CROSS-SITE REQUEST FORGERY (CSRF) vulnerability can allow execution of unauthorized actions on the device such as configuration parameter changes, and saving modified configuration.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	10.0 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 31%)
CISA exploited list	No
Weakness	CWE-352
Published	2017-02-13
Last modified	2026-06-17

Publisher (CNA): ICS-CERT · Vendor: carlosgavazzi

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-02-13 21:59 UTCPublished CVE record published
2026-06-17 01:20 UTCUpdated Record last modified

carlosgavazzi vmu-c em firmware MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

carlosgavazzi vmu-c pv firmware MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-5145?

vmu-c em firmware: mitigate or apply the listed mitigation; vmu-c pv firmware: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-5145 being exploited?

CVE-2017-5145 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-5145 affect?

CVE-2017-5145 affects vmu-c em firmware, vmu-c pv firmware. Severity is critical (CVSS 10.0). 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. Successful exploitation of this CROSS-SITE REQUEST FORGERY (CSRF) vulnerability can allow execution of unauthor

How urgent is CVE-2017-5145?

Priority 57/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2017-5146 HIGH 7.5 MITIGATE MITIGATE An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to fir
CVE-2017-5144 CRITICAL 9.8 MITIGATE MITIGATE An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to fir

References

← Back to latest CVEs