dbcve.org
Inrouter302 FirmwareOperating system · Inhandnetworks

CVE-2023-22600

HIGH · 8.1 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 →
90/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-284: Improper Access Control. They allow unauthenticated devices to subscribe to MQTT topics on the same network as the device manager. An unauthorized user who knows of an existing topic name could send and receive messages to and from that topic. This includes the ability to send GET/SET configuration commands, reboot commands, and push firmware updates.

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

InHand Networks InRouter 302 and 615 devices contain an improper access control vulnerability (CWE-284) in their MQTT service implementation. Unauthenticated devices on the same network as the device manager can subscribe to MQTT topics if they know the topic name, enabling them to send and receive sensitive commands including GET/SET configuration operations, device reboots, and firmware updates without any authentication.

MitigationUpdate the device firmware to version IR302 V3.5.56 or InRouter6XX-S-V2.3.0.r5542 or later. If immediate patching is not feasible, implement network segmentation and firewall rules to restrict access to the MQTT broker to only authorized management stations.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 device model
    Log into the device web interface or check the device label to confirm whether it is an InRouter302 or InRouter615-S model.
    Affected if Device is an InRouter302 or InRouter615-S model.
  2. Check firmware version on InRouter302
    Access the device CLI or web interface and navigate to System Status or Firmware Information to view the installed firmware version. Compare against 3.5.56.
    Affected if Installed firmware version is lower than 3.5.56 on an InRouter302.
  3. Check firmware version on InRouter615-S
    Access the device CLI or web interface and navigate to System Status or Firmware Information to view the installed firmware version. Compare against 2.3.0.r5542.
    Affected if Installed firmware version is lower than 2.3.0.r5542 on an InRouter615-S.
  4. Verify MQTT service status
    Check if the MQTT service is enabled on the device. In the web interface, go to Services or Protocol Settings and confirm whether MQTT Broker/Client is turned on.
    Affected if MQTT service is enabled on the device.
  5. Check MQTT port accessibility
    From a host on the same network segment as the device, attempt to connect to the MQTT port (default 1883) using tools like netcat or nmap: nc -zv <device_ip> 1883 or nmap -p 1883 <device_ip>.
    Affected if The MQTT port 1883 is accessible from untrusted network segments.

You are affected if you have an InRouter302 with firmware below 3.5.56 or an InRouter615-S with firmware below 2.3.0.r5542, and the MQTT service is enabled and accessible from your network.

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

Update the device firmware to version IR302 V3.5.56 or InRouter6XX-S-V2.3.0.r5542 or later. If immediate patching is not feasible, implement network segmentation and firewall rules to restrict access to the MQTT broker to only authorized management stations.

Recommended fix High confidence

InRouter 302: IR302 V3.5.56 or later; InRouter 615-S: InRouter6XX-S-V2.3.0.r5542 or later

  1. Identify the exact model and current firmware version of the InRouter device (302 or 615-S)
  2. Navigate to InHand Networks official support or download portal to obtain the fixed firmware: IR302 V3.5.56 or later for InRouter 302, InRouter6XX-S-V2.3.0.r5542 or later for InRouter 615-S
  3. Review the InHand Networks firmware upgrade documentation for your specific model
  4. Upload the new firmware file through the device's web-based management interface or CLI following vendor procedures
  5. After reboot, verify the firmware version has been updated to the fixed release
  6. If available, disable or restrict MQTT topic subscriptions to prevent unauthorized access on the network
  7. Verify the device is functioning normally after the upgrade
Caveat Firmware upgrades may temporarily disrupt connectivity; ensure backup of configuration before upgrading and test in controlled environment first

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

Fix this in Inrouter302 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22600 — 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-22600 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