# CVE-2022-2634: Digi ConnectPort X2D

> Attackers can upload and execute Python files on Digi ConnectPort X2D devices due to missing access controls in the web application.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-rpmr-9m52-wm2f

## What is CVE-2022-2634?

CVE-2022-2634 is a critical missing authorization vulnerability in Digi ConnectPort X2D, published on 9 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker may be able to execute malicious actions due to the lack of device access protections and device permissions when using the web application. This could lead to uploading python files which can be later executed.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2022-2634?

It affects 1 product.


Products: Digi Connectport X2d Firmware.

## How do I fix CVE-2022-2634?

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

## Is CVE-2022-2634 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2634 and fix it if it is affected.

What it is: CVE-2022-2634 is a critical missing authorization vulnerability in Digi ConnectPort X2D, published on 9 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2634 in the wild and no public exploit code.

Affected product: Digi ConnectPort X2D. 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-2022-2634/ (Markdown: https://insights.sbomify.com/CVE-2022-2634/index.md)
```

## Sources

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

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