CVE-2021-37188: An issue was discovered on Digi TransPort devices through 2021-07-21.
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered on Digi TransPort devices through 2021-07-21. An authenticated attacker may load customized firmware (because the bootloader does not verify that it is authentic), changing the behavior of the gateway.
- Published
- Dec 10, 2021
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-345
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| digi | transport dr64 firmware | cpe:2.3:o:digi:transport_dr64_firmware |
| digi | transport dr64 | cpe:2.3:h:digi:transport_dr64 |
| digi | transport sr44 | cpe:2.3:h:digi:transport_sr44 |
| digi | transport vc74 firmware | cpe:2.3:o:digi:transport_vc74_firmware |
| digi | transport vc74 | cpe:2.3:h:digi:transport_vc74 |
| digi | transport wr11 firmware | cpe:2.3:o:digi:transport_wr11_firmware |
| digi | transport wr11 | cpe:2.3:h:digi:transport_wr11 |
| digi | transport wr11 xt firmware | cpe:2.3:o:digi:transport_wr11_xt_firmware |
| digi | transport wr11 xt | cpe:2.3:h:digi:transport_wr11_xt |
| digi | transport wr21 firmware | cpe:2.3:o:digi:transport_wr21_firmware |
| digi | transport wr21 | cpe:2.3:h:digi:transport_wr21 |
| digi | transport wr31 firmware | cpe:2.3:o:digi:transport_wr31_firmware |
and 5 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- digi transport dr64 firmwareup to 5.2.4.9 inclusive
- digi transport dr64 firmwareall versions
- digi transport vc74 firmwareup to 5.2.4.9 inclusive
- digi transport wr11 firmwareup to 8.2.1.3 inclusive
- digi transport wr11 xt firmwareup to 8.2.1.3 inclusive
- digi transport wr21 firmwareup to 8.2.1.3 inclusive
- digi transport wr31 firmwareup to 8.2.1.3 inclusive
- digi transport wr41 firmware5.0.0.0 and later · up to 5.2.4.6 inclusive
- digi transport wr41 firmware6.0.0.0 and later · up to 6.1.3.5 inclusive
- digi transport wr41 firmware8.0.0.0 and later · up to 8.3.1.2 inclusive
- digi transport wr44 firmwareup to 8.3.1.2 inclusive
Same product
digi: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-35978An issue was discovered in Digi TransPort DR64, SR44 VC74, and WR.40Plan
- CVE-2021-37187An issue was discovered on Digi TransPort devices through 2021-07-21.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.