CVE-2021-37187
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 · uneditedAn issue was discovered on Digi TransPort devices through 2021-07-21. An authenticated attacker may read a password file (with reversible passwords) from the device, which allows decoding of other users' passwords.
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 confidenceDigi TransPort devices through mid-2021 allow authenticated attackers to read a password file containing reversible (readable or weakly encrypted) passwords, enabling decryption of other users' credentials.
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<= 5.2.4.9all versions<= 5.2.4.9<= 8.2.1.3<= 8.2.1.3<= 8.2.1.3<= 8.2.1.3>= 5.0.0.0, <= 5.2.4.6>= 6.0.0.0, <= 6.1.3.5>= 8.0.0.0, <= 8.3.1.2<= 8.3.1.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Digi TransPort device modelLog into the device or check the device label/documentation to determine the exact model (Dr64, Vc74, Wr11, Wr11 Xt, Wr21, Wr31, Wr41, or Wr44)Affected if The device is one of the listed models (Dr64, Vc74, Wr11, Wr11 Xt, Wr21, Wr31, Wr41, or Wr44)
-
Determine the installed firmware versionAccess the device web interface or CLI and navigate to the firmware/version information section, typically found under Status, System, or About menuAffected if Unable to determine firmware version or version is within affected ranges
-
Check Dr64 firmware versionIf device is Dr64, compare installed version to <= 5.2.4.9Affected if Firmware version is 5.2.4.9 or earlier, or is any version (all versions affected)
-
Check Vc74 firmware versionIf device is Vc74, compare installed version to <= 5.2.4.9Affected if Firmware version is 5.2.4.9 or earlier
-
Check Wr11, Wr11 Xt, Wr21, Wr31 firmware versionIf device is Wr11, Wr11 Xt, Wr21, or Wr31, compare installed version to <= 8.2.1.3Affected if Firmware version is 8.2.1.3 or earlier
-
Check Wr41 firmware versionIf device is Wr41, compare installed version to the affected ranges: <= 5.2.4.6, 6.0.0.0 to 6.1.3.5, or 8.0.0.0 to 8.3.1.2Affected if Firmware version falls within any of the three affected ranges (5.0.0.0-5.2.4.6, 6.0.0.0-6.1.3.5, or 8.0.0.0-8.3.1.2)
The device is affected if it is a Digi TransPort model (Dr64, Vc74, Wr11, Wr11 Xt, Wr21, Wr31, Wr41, or Wr44) and its firmware version falls within the specified affected ranges for that model.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate Digi TransPort devices to firmware versions that implement proper password hashing and encryption; restrict access to privileged accounts and review user credentials.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37187 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-37187 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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