InRouter 302: Use of Insufficiently Random Values
CVE-2023-22601 is a high-severity use of insufficiently random values vulnerability in InRouter 302 from InHand Networks, with a CVSS 3.1 base score of 8.6 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version IR302 V3.5.56 as the first without the flaw, so updating InRouter 302 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.6% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update InRouter 302 to IR302 V3.5.56 or a later version.
- Update InRouter 615 to InRouter6XX-S-V2.3.0.r5542 or a later version.
- Update Inrouter302 Firmware to 3.5.56 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| InHand Networks | InRouter 302 | before IR302 V3.5.56 | IR302 V3.5.56 |
| InHand Networks | InRouter 615 | before InRouter6XX-S-V2.3.0.r5542 | InRouter6XX-S-V2.3.0.r5542 |
| Inhandnetworks | Inrouter302 Firmware | before 3.5.56 | 3.5.56 |
| Inhandnetworks | Inrouter615-s Firmware | before 2.3.0.r5542 | 2.3.0.r5542 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 10.0 | Critical | CNA (hq.dhs.gov) |
| CVSS 3.1 | 8.6 | High | NVD |
Official description
InHand Networks InRouter 302, prior to version IR302 V3.5.56, and InRouter 615, prior to version InRouter6XX-S-V2.3.0.r5542, contain vulnerability CWE-330: Use of Insufficiently Random Values. They do not properly randomize MQTT ClientID parameters. An unauthorized user could calculate this parameter and use it to gather additional information about other InHand devices managed on the same cloud platform.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Insufficiently Random Values
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
How developers prevent this class of flaw
- Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds. In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts. Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a random enough number.
- Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.
- Use products or modules that conform to FIPS 140-2 to avoid obvious entropy problems. Consult FIPS 140-2 Annex C (Approved Random Number Generators).
More Use of Insufficiently Random Values vulnerabilities (CWE-330)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/uscert/ics/advisories/icsa-23-012-03Third Party Advisory, US Government Resource
Other vulnerabilities in InRouter 302
- 8.1 High severity
- 9.1 Critical severity
- 7.2 High severity
Recent Use of Insufficiently Random Values vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
- 9.1 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.