# CVE-2017-20184: Carlo Gavazzi Powersoft prone to Path Traversal

> An unauthenticated remote attacker can download arbitrary files from Carlo Gavazzi Powersoft devices due to a path traversal vulnerability.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2023
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-mr2h-vgpg-wjv6

## What is CVE-2017-20184?

CVE-2017-20184 is a high-severity path traversal vulnerability in Carlo Gavazzi Powersoft, published on 4 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Carlo Gavazzi Powersoft up to version 2.1.1.1 allows an unauthenticated, remote attacker to download any file from the affected device.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Gavazzionline Powersoft.

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

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

## Is CVE-2017-20184 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20184 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20184 is a high-severity path traversal vulnerability in Carlo Gavazzi Powersoft, published on 4 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20184 exists.

Affected product: Carlo Gavazzi Powersoft. 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-20184/ (Markdown: https://insights.sbomify.com/CVE-2017-20184/index.md)
```

## Sources

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

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