# CVE-2021-37189: Security feature bypass in n/a

> Missing Secure cookie attribute on Digi TransPort Gateways allows session hijacking via cleartext HTTP transmission.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5xj4-c9mm-32pr

## What is CVE-2021-37189?

CVE-2021-37189 is a high-severity vulnerability in n/a, published on 10 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 6 products.


Products: 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-37189?

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

## Is CVE-2021-37189 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-37189 is a high-severity vulnerability in n/a, published on 10 Dec 2021. 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-2021-37189 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-37189/ (Markdown: https://insights.sbomify.com/CVE-2021-37189/index.md)
```

## Sources

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

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