# CVE-2019-19229: Path traversal in n/a

> Attackers can exploit a directory traversal vulnerability in the web interface to read arbitrary files from the solar inverter.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f268-9fq5-h8qf

## What is CVE-2019-19229?

CVE-2019-19229 is a medium-severity path traversal vulnerability in n/a, published on 4 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

admincgi-bin/service.fcgi on Fronius Solar Inverter devices before 3.14.1 (HM 1.12.1) allows action=download&filename= Directory Traversal.

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

## Which versions are affected by CVE-2019-19229?

It affects 66 products.


Products: Fronius Datamanager Box 2.0 Firmware, Fronius Eco 25.0-3-S Firmware, Fronius Eco 27.0-3-S Firmware, Fronius Galvo 1.5-1 208-240 Firmware, Fronius Galvo 1.5-1 Firmware, Fronius Galvo 2.0-1 208-240 Firmware, Fronius Galvo 2.0-1 Firmware, Fronius Galvo 2.5-1 208-240 Firmware, Fronius Galvo 2.5-1 Firmware, Fronius Galvo 3.0-1 Firmware, Fronius Galvo 3.1-1 208-240 Firmware, Fronius Galvo 3.1-1 Firmware, Fronius Primo 10.0-1 208-240 Firmware, Fronius Primo 11.4-1 208-240 Firmware, Fronius Primo 12.5-1 208-240 Firmware, Fronius Primo 15.0-1 208-240 Firmware, Fronius Primo 3.0-1 Firmware, Fronius Primo 3.5-1 Firmware, Fronius Primo 3.6-1 Firmware, Fronius Primo 3.8-1 208-240 Firmware and 46 more.

## How do I fix CVE-2019-19229?

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

## Is CVE-2019-19229 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19228](https://insights.sbomify.com/CVE-2019-19228/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19229 and fix it if it is affected.

What it is: CVE-2019-19229 is a medium-severity path traversal vulnerability in n/a, published on 4 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19229 in the wild and no public exploit code.

Affected product: n/a. 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-2019-19229/ (Markdown: https://insights.sbomify.com/CVE-2019-19229/index.md)
```

## Sources

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

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