# CVE-2017-5144: Missing authorization in Carlo Gavazzi VMU-C EM and VMU-C PV

> Attackers can access application functions without authentication on Carlo Gavazzi VMU-C devices, requiring firmware upgrades to mitigate.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gm4w-w2wh-hv48

## What is CVE-2017-5144?

CVE-2017-5144 is a critical missing authorization vulnerability in Carlo Gavazzi VMU-C EM and VMU-C PV, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2017-5144?

It affects 2 products.


Products: Carlosgavazzi Vmu-C Em Firmware, Carlosgavazzi Vmu-C Pv Firmware.

## How do I fix CVE-2017-5144?

No fix has been published for CVE-2017-5144 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-5144 being exploited?

There is no known exploitation of CVE-2017-5144 in the wild and no public exploit code.

## Other vulnerabilities in Carlo Gavazzi VMU-C EM and VMU-C PV

- [CVE-2017-5145](https://insights.sbomify.com/CVE-2017-5145/): Cross-site request forgery in Carlo Gavazzi VMU-C EM and VMU-C PV (critical 10.0)
- [CVE-2017-5146](https://insights.sbomify.com/CVE-2017-5146/): Information disclosure in Carlo Gavazzi VMU-C EM and VMU-C PV (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5144 and fix it if it is affected.

What it is: CVE-2017-5144 is a critical missing authorization vulnerability in Carlo Gavazzi VMU-C EM and VMU-C PV, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5144 in the wild and no public exploit code.

Affected product: Carlo Gavazzi VMU-C EM and VMU-C PV. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-5144/ (Markdown: https://insights.sbomify.com/CVE-2017-5144/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5144
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5144
- OSV: https://osv.dev/vulnerability/CVE-2017-5144

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-5144/
Summaries are generated and may contain mistakes; the official description above is the record.