dbcve.org
Transport Wr11 FirmwareOperating system · Digi

CVE-2021-37189

HIGH · 7.5 CVSS v3.1 Published 2021-12-10
Fix available
A fix is available. Upgrade to 6.0.0.0 or later.
See remediation →
84/100
Remediation priority · High
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 issue was discovered on Digi TransPort Gateway devices through 5.2.13.4. They do not set the Secure attribute for sensitive cookies in HTTPS sessions, which could cause the user agent to send those cookies in cleartext over an HTTP session.

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 · high confidence

Digi TransPort Gateway devices through version 5.2.13.4 fail to set the Secure attribute on sensitive cookies during HTTPS sessions. This allows browsers to transmit these cookies over unencrypted HTTP connections, exposing session credentials in cleartext.

MitigationConfigure the web application or server to set the Secure flag on all sensitive cookies, ensuring they are only transmitted over encrypted HTTPS connections.

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
Transport Wr11 FirmwareOperating system
Affected:< 6.0.0.0
Transport Wr11 Xt FirmwareOperating system
Affected:< 6.0.0.0
Transport Wr21 FirmwareOperating system
Affected:< 6.0.0.0
Transport Wr31 FirmwareOperating system
Affected:< 6.0.0.0
Transport Wr41 FirmwareOperating system
Affected:< 6.0.0.0
Transport Wr44 FirmwareOperating system
Affected:< 6.0.0.0

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
None
Availability
None

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

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 Digi Transport device model
    Access the device web interface or CLI and note the exact model name (Wr11, Wr11 Xt, Wr21, Wr31, Wr41, or Wr44)
    Affected if The device model matches one of the affected models listed in the CVE
  2. Determine the installed firmware version
    Log into the device web interface and navigate to the Status or System Information page, or use the CLI command 'show version' to retrieve the firmware version
    Affected if The firmware version cannot be determined or is below 6.0.0.0
  3. Compare firmware version against the affected range
    Check if the installed firmware version is less than 6.0.0.0 by comparing the version numbers
    Affected if The firmware version is < 6.0.0.0 for any of the affected models (Wr11, Wr11 Xt, Wr21, Wr31, Wr41, Wr44)
  4. Verify HTTPS is enabled and inspect cookie headers
    Access the device web interface over HTTPS, open browser developer tools (F12), go to the Network tab, and examine the response headers for Set-Cookie directives. Check if the Secure attribute is present on session cookies
    Affected if Sensitive cookies are set without the Secure attribute when communicating over HTTPS

A user is affected if they are running any Digi Transport Wr11, Wr11 Xt, Wr21, Wr31, Wr41, or Wr44 device with firmware version below 6.0.0.0 and the device web interface sets cookies without the Secure flag.

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 6.0.0.0 or later
Fixed in 6.0.0.0
Interim mitigation

Configure the web application or server to set the Secure flag on all sensitive cookies, ensuring they are only transmitted over encrypted HTTPS connections.

Recommended fix Moderate confidence

Firmware version 6.0.0.0 or later for Digi TransPort WR11/WR11 Xt/WR21/WR31/WR41/WR44

  1. 1. Identify the exact model of your Digi TransPort device (WR11, WR11 Xt, WR21, WR31, WR41, or WR44)
  2. 2. Check the current firmware version installed on the device through the administrative web interface or CLI
  3. 3. Navigate to the official Digi support website (www.digi.com) and locate the firmware download section for your specific device model
  4. 4. Download firmware version 6.0.0.0 or later for your device
  5. 5. Back up the current device configuration before performing the upgrade
  6. 6. Upload and apply the new firmware through the device's web interface or using Digi's firmware update procedure
  7. 7. Verify the upgrade was successful and confirm the new firmware version
  8. 8. Test that cookies are now properly handled with the Secure attribute in HTTPS sessions
Caveat Review Digi release notes for any configuration or feature changes between your current version and 6.0.0.0

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

Fix this in Transport Wr11 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-37189 — 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-2021-37189 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