# CVE-2020-6975: File upload in Digi International ConnectPort LTS 32 MEI

> An attacker can upload malicious files to the Digi ConnectPort LTS 32 MEI device, potentially leading to code execution.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j2wg-qg38-9vmr

## What is CVE-2020-6975?

CVE-2020-6975 is a medium-severity vulnerability in Digi International ConnectPort LTS 32 MEI, published on 12 Feb 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Digi International ConnectPort LTS 32 MEI, Firmware Version 1.4.3 (82002228_K 08/09/2018), bios Version 1.2. Successful exploitation of this vulnerability could allow an attacker to upload a malicious file to the application.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2020-6975?

It affects 2 products.


Products: Digi Connectport Lts 32 Mei Bios, Digi Connectport Lts 32 Mei Firmware.

## How do I fix CVE-2020-6975?

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

## Is CVE-2020-6975 being exploited?

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

## Other vulnerabilities in Digi International ConnectPort LTS 32 MEI

- [CVE-2020-6973](https://insights.sbomify.com/CVE-2020-6973/): Cross-site scripting in Digi International ConnectPort LTS 32 MEI (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6975 and fix it if it is affected.

What it is: CVE-2020-6975 is a medium-severity vulnerability in Digi International ConnectPort LTS 32 MEI, published on 12 Feb 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6975 in the wild and no public exploit code.

Affected product: Digi International ConnectPort LTS 32 MEI. 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-2020-6975/ (Markdown: https://insights.sbomify.com/CVE-2020-6975/index.md)
```

## Sources

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

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