# CVE-2024-50627: File upload in n/a

> An attacker on the local network can upload and execute malicious files to gain unauthorized system access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2024
- **Updated:** 11 Dec 2024
- **Also known as:** GHSA-vq87-xfrv-42wp

## What is CVE-2024-50627?

CVE-2024-50627 is a high-severity vulnerability in n/a, published on 9 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Digi ConnectPort LTS before 1.4.12. A Privilege Escalation vulnerability exists in the file upload feature. It allows an attacker on the local area network (with specific permissions) to upload and execute malicious files, potentially leading to unauthorized system access.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2024-50627?

It affects 1 product.


Products: Digi Connectport Lts Firmware.

## How do I fix CVE-2024-50627?

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

## Is CVE-2024-50627 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-50626](https://insights.sbomify.com/CVE-2024-50626/): Path traversal in n/a (high 8.8)
- [CVE-2024-50628](https://insights.sbomify.com/CVE-2024-50628/): Missing authorization in n/a (high 8.8)
- [CVE-2024-50625](https://insights.sbomify.com/CVE-2024-50625/): File upload in n/a (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50627 and fix it if it is affected.

What it is: CVE-2024-50627 is a high-severity vulnerability in n/a, published on 9 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50627 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-2024-50627/ (Markdown: https://insights.sbomify.com/CVE-2024-50627/index.md)
```

## Sources

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

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