# CVE-2017-6565: File upload in n/a

> An attacker with roleDiag access can upload malicious files to Franklin Fueling Systems TS-550 evo devices due to lack of sanitization, potentially leading to code execution.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 1 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6523-39wf-j4g3

## What is CVE-2017-6565?

CVE-2017-6565 is a high-severity vulnerability in n/a, published on 1 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On Franklin Fueling Systems TS-550 evo 2.3.0.7332 devices, the roleDiag user, which can be obtained by exploiting CVE-2013-7247, has the ability to upload files to the server hosting the web service. As no sanitization checks are in place, an attacker can upload a malicious payload.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Franklinfueling Ts-550 Evo Firmware.

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

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

## Is CVE-2017-6565 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-5846](https://insights.sbomify.com/CVE-2023-5846/): Use of Password Hash With Insufficient Computational Effort in Franklin Fueling System TS-550 (high 8.3)
- [CVE-2021-46420](https://insights.sbomify.com/CVE-2021-46420/): Path traversal in n/a (high 7.5)
- [CVE-2021-46421](https://insights.sbomify.com/CVE-2021-46421/): Path traversal in n/a (high 7.5)
- [CVE-2017-6564](https://insights.sbomify.com/CVE-2017-6564/): Missing authorization in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6565 is a high-severity vulnerability in n/a, published on 1 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6565 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-2017-6565/ (Markdown: https://insights.sbomify.com/CVE-2017-6565/index.md)
```

## Sources

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

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