dbcve.org
Inrouter302 FirmwareOperating system · Inhandnetworks

CVE-2023-22599

CRITICAL · 9.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 →
100/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-760: Use of a One-way Hash with a Predictable Salt. They  send MQTT credentials in response to HTTP/HTTPS requests from the cloud platform. These credentials are encoded using a hardcoded string into an MD5 hash. This string could be easily calculated by an unauthorized user who spoofed sending an HTTP/HTTPS request to the devices. This could result in the affected devices being temporarily disconnected from the cloud platform and allow the user to receive MQTT commands with potentially sensitive information.

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 affected InRouter devices use a hardcoded string as salt when hashing MQTT credentials with MD5. Since the salt is predictable and hardcoded in the firmware, an attacker who spoofs an HTTP/HTTPS request to the device can calculate the hash and obtain valid credentials. This allows the attacker to disconnect the device from the cloud platform and intercept potentially sensitive MQTT commands.

MitigationUpgrade InRouter 302 to version IR302 V3.5.56 or later, and InRouter 615 to version InRouter6XX-S-V2.3.0.r5542 or later. Additionally, consider network segmentation and monitoring for suspicious MQTT traffic.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the InRouter model
    Locate the device label or access the device management interface to confirm whether the device is an InRouter 302 or InRouter 615 S model.
    Affected if The device is an InRouter 302 or InRouter 615 S model.
  2. Check the installed firmware version
    Access the device web interface or CLI and navigate to the firmware or system information section to retrieve the current firmware version number.
    Affected if The firmware version is below 3.5.56 for InRouter 302, or below 2.3.0.r5542 for InRouter 615 S.
  3. Verify MQTT client configuration
    Access the device settings and check whether the MQTT client feature is enabled or configured to connect to a cloud platform.
    Affected if MQTT is enabled and configured on the device.
  4. Inspect firmware for hardcoded salt string
    If you have access to the firmware image or can extract it, search the binary or configuration files for the hardcoded salt string used in MD5 hashing of MQTT credentials.
    Affected if A hardcoded or static salt string is present in the firmware.

A user is affected if they have an InRouter 302 with firmware below 3.5.56 or an InRouter 615 S below 2.3.0.r5542, with MQTT client enabled and a hardcoded salt present in the firmware.

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 IR302 V3.5.56 or later, and InRouter 615 to version InRouter6XX-S-V2.3.0.r5542 or later. Additionally, consider network segmentation and monitoring for suspicious MQTT traffic.

Recommended fix High confidence

InRouter302: upgrade to IR302 V3.5.56 or later; InRouter615 S: upgrade to InRouter6XX-S-V2.3.0.r5542 or later

  1. Identify the current firmware version of the InRouter 302 or InRouter 615 S device
  2. Download the fixed firmware version (IR302 V3.5.56 or InRouter6XX-S-V2.3.0.r5542) from InHand Networks official support portal
  3. Review InHand Networks official firmware upgrade documentation for the specific device model
  4. Follow the vendor-provided firmware upgrade procedure to apply the update to the device
  5. After upgrading, verify that the firmware version has been successfully updated to the fixed release
  6. Confirm that the MQTT credential vulnerability is resolved by testing that credentials are no longer using a hardcoded salt in the MD5 hash

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

Fix this in Inrouter302 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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