# CVE-2021-37187: Information disclosure in n/a

> An authenticated attacker can read a password file to decode other users' passwords on Digi TransPort devices.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j8g6-7jj6-7w7v

## What is CVE-2021-37187?

CVE-2021-37187 is a medium-severity vulnerability in n/a, published on 10 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An 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.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2021-37187?

It affects 8 products.


Products: Digi Transport Dr64 Firmware, Digi Transport Vc74 Firmware, Digi Transport Wr11 Firmware, Digi Transport Wr11 Xt Firmware, Digi Transport Wr21 Firmware, Digi Transport Wr31 Firmware, Digi Transport Wr41 Firmware, Digi Transport Wr44 Firmware.

## How do I fix CVE-2021-37187?

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

## Is CVE-2021-37187 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-35978](https://insights.sbomify.com/CVE-2021-35978/): Command injection in n/a (critical 9.8)
- [CVE-2021-37188](https://insights.sbomify.com/CVE-2021-37188/): Security feature bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-37187 and fix it if it is affected.

What it is: CVE-2021-37187 is a medium-severity vulnerability in n/a, published on 10 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-37187 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-2021-37187/ (Markdown: https://insights.sbomify.com/CVE-2021-37187/index.md)
```

## Sources

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

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