Tropos Wireless Mesh Routers Insufficient Entropy
Mesh OS before 7.9.1.1 on Tropos wireless mesh routers does not use a sufficient source of entropy for SSH keys, which makes it easier for man-in-the-middle attackers to spoof a device or modify a client-server data stream by leveraging knowledge of a key from a product installation elsewhere.
- Published
- Dec 18, 2012
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 61th percentile
- CWE
- CWE-310
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CNA vs NVD score
- NVD
- 6.1
- CNA · icscert
- 6.1
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| tropos | mesh os | cpe:2.3:o:tropos:mesh_os |
| tropos | 1310 distrubution automation mesh router | cpe:2.3:h:tropos:1310_distrubution_automation_mesh_router |
| tropos | 1410 mesh router | cpe:2.3:h:tropos:1410_mesh_router |
| tropos | 1410 wireless mesh router | cpe:2.3:h:tropos:1410_wireless_mesh_router |
| tropos | 3310 indoor mesh router | cpe:2.3:h:tropos:3310_indoor_mesh_router |
| tropos | 3320 indoor mesh router | cpe:2.3:h:tropos:3320_indoor_mesh_router |
| tropos | 4310 mobile mesh router | cpe:2.3:h:tropos:4310_mobile_mesh_router |
| tropos | 6310 mesh router | cpe:2.3:h:tropos:6310_mesh_router |
| tropos | 6320 mesh router | cpe:2.3:h:tropos:6320_mesh_router |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tropos 1310 distrubution automation mesh routerall versions
- tropos 1410 mesh routerall versions
- tropos 1410 wireless mesh routerall versions
- tropos 3310 indoor mesh routerall versions
- tropos 3320 indoor mesh routerall versions
- tropos 4310 mobile mesh routerall versions
- tropos 6310 mesh routerall versions
- tropos 6320 mesh routerall versions
- tropos mesh osup to 7.9.1 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.
Tropos Mesh OS
- before 7.9.1.1affected
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- research group composedNadia Heninger (University of California at San Diego), Zakir Durumeric (Universityfinder
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
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- C · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- High
- Confidentiality impact
- C
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
AV:N/AC:H/Au:N/C:C/I:P/A:N
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.cisa.gov/news-events/ics-advisories/icsa-12-297-01
- www.us-cert.gov/control_systems/pdf/ICSA-12-297-01.pdf
Vendor advisories and official records. Exploit/PoC links are deliberately left out.