dbcve.org
Connectport X2d FirmwareOperating system · Digi

CVE-2022-2634

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-10
Fix available
A fix is available. Upgrade to 2020-01-01 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a critical access control vulnerability in a web application where missing device access protections and permission checks allow unauthorized users to upload Python files. The uploaded files can then be executed, enabling remote code execution (RCE) on the underlying system.

MitigationImplement proper authentication and authorization mechanisms to verify user identity and permissions before allowing any file upload operations. Add strict file type validation, restrict upload directories, and disable script execution in upload locations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Connectport X2d FirmwareOperating system
Affected:< 2020-01-01

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device's web interface, check the device label, or run CLI commands like 'show system' to confirm the device is a Digi Connectport X2d
    Affected if The device is a Digi Connectport X2d
  2. Determine firmware version
    Access the web interface status page or run 'show version' command via CLI to check the firmware build date
    Affected if Firmware build date is before January 1, 2020
  3. Confirm web application is enabled
    Attempt to access the device's web interface over HTTP or HTTPS
    Affected if Web interface is running and accessible
  4. Test file upload endpoint access controls
    Navigate to the file upload functionality in the web interface, or probe common upload paths without authentication
    Affected if Upload functionality is accessible without requiring user authentication or proper authorization checks

A defender is affected if they have a Digi Connectport X2d device running firmware dated before 2020-01-01 with the web-based file upload feature exposed without proper access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2020-01-01 or later
Fixed in 2020-01-01
Interim mitigation

Implement proper authentication and authorization mechanisms to verify user identity and permissions before allowing any file upload operations. Add strict file type validation, restrict upload directories, and disable script execution in upload locations.

Recommended fix Moderate confidence

Connectport X2d Firmware version 2020-01-01 or later

  1. 1. Identify the current firmware version of the Connectport X2d device by accessing the web interface or using the device's management console.
  2. 2. Navigate to Digi's official support website or contact Digi technical support to obtain the firmware version dated 2020-01-01 or later.
  3. 3. Back up the current device configuration to ensure settings are preserved during the upgrade process.
  4. 4. Access the device's firmware update section in the web-based management interface.
  5. 5. Upload and install the firmware version 2020-01-01 or later, following the manufacturer's documented upgrade procedure.
  6. 6. After the firmware update completes, verify the device is operational and confirm the new firmware version is installed.
  7. 7. Validate that the web application now properly enforces access controls and permissions to prevent unauthorized Python file uploads.
Caveat Review Digi release notes for any configuration or feature changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connectport X2d Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2634 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2634 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data