dbcve.org
Inrouter302 FirmwareOperating system · Inhandnetworks

CVE-2023-22601

HIGH · 8.6 CVSS v3.1 Published 2023-01-12
Fix available
A fix is available. Upgrade to 2.3.0.r5542 / 3.5.56 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The InRouter 302 and InRouter 615 fail to properly randomize MQTT ClientID parameters when connecting to InHand's cloud platform. The ClientID can be predicted or calculated by an unauthorized user, allowing them to impersonate legitimate devices and gather information about other InHand devices managed on the same cloud platform.

MitigationUpgrade InRouter 302 to version V3.5.56 or later, and InRouter 615 to version InRouter6XX-S-V2.3.0.r5542 or later. These versions properly randomize the MQTT ClientID parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Inrouter302 FirmwareOperating system
Affected:< 3.5.56
Inrouter615 S FirmwareOperating system
Affected:< 2.3.0.r5542

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Check the InRouter model number (302 or 615 S) in the device web interface, CLI, or physical label
    Affected if Device is not an InRouter 302 or InRouter 615 S model
  2. Check the installed firmware version
    Access the device web interface under System > Firmware/Version, or run 'show version' in CLI, or check the firmware file name if manually flashed
    Affected if Firmware version is below 3.5.56 for InRouter 302, or below 2.3.0.r5542 for InRouter 615 S
  3. Verify MQTT cloud connection is configured
    Check device settings for InHand Cloud / InRouter Cloud / MQTT cloud connectivity configuration, typically under Network > MQTT or Cloud Services settings
    Affected if MQTT connection to InHand cloud platform is enabled and configured
  4. Inspect the MQTT ClientID parameter
    Examine MQTT client configuration or captured MQTT CONNECT packets to view the ClientID value; check if it appears predictable, sequential, or based on device serial/MAC rather than randomized
    Affected if The ClientID follows a predictable pattern (e.g., contains serial number, MAC address, or incremental numbers) rather than a random string

Device is affected if it is an InRouter 302 with firmware below 3.5.56 or InRouter 615 S with firmware below 2.3.0.r5542, and has MQTT cloud connectivity enabled with a non-randomized ClientID.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.0.r5542 / 3.5.56 or later
Fixed in 2.3.0.r55423.5.56
Interim mitigation

Upgrade InRouter 302 to version V3.5.56 or later, and InRouter 615 to version InRouter6XX-S-V2.3.0.r5542 or later. These versions properly randomize the MQTT ClientID parameter.

Recommended fix High confidence

IR302 V3.5.56 or InRouter6XX-S-V2.3.0.r5542

  1. 1. Identify the exact InRouter model number (IR302 or IR615-S) and current firmware version via the device web UI or console
  2. 2. Download the firmware update from InHand Networks official support channels: IR302 V3.5.56 or InRouter6XX-S-V2.3.0.r5542
  3. 3. Access the device web management interface and navigate to System > Firmware Upgrade (or use TFTP as documented by InHand)
  4. 4. Upload the downloaded firmware file and initiate the upgrade process
  5. 5. Wait for the device to reboot and verify the new firmware version is installed
  6. 6. Confirm that MQTT ClientID parameters are now properly randomized by inspecting MQTT traffic or consulting vendor documentation
Caveat Standard firmware upgrade risk applies - ensure backup of configuration and plan for brief downtime

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Inrouter302 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22601 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-22601 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data