# CVE-2023-22599: Hardcoded credentials in InRouter 302

> An attacker can spoof requests to obtain hardcoded MQTT credentials, leading to device disconnection and exposure of sensitive command data.

- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2023
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-3q43-m4hc-qh5p

## What is CVE-2023-22599?

CVE-2023-22599 is a high-severity vulnerability in InHand Networks InRouter 302, published on 12 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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-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.

Weakness: CWE-760 (Use of a One-Way Hash with a Predictable Salt)

## Which versions are affected by CVE-2023-22599?

It affects 2 products.


Products: Inhandnetworks Inrouter302 Firmware, Inhandnetworks Inrouter615-S Firmware.

## How do I fix CVE-2023-22599?

No fix has been published for CVE-2023-22599 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-22599 being exploited?

There is no known exploitation of CVE-2023-22599 in the wild and no public exploit code.

## Other vulnerabilities in InHand Networks InRouter 302

- [CVE-2023-22600](https://insights.sbomify.com/CVE-2023-22600/): Missing authorization in InRouter 302 (critical 10.0)
- [CVE-2023-22601](https://insights.sbomify.com/CVE-2023-22601/): Information disclosure in InRouter 302 (critical 10.0)
- [CVE-2022-21809](https://insights.sbomify.com/CVE-2022-21809/): File upload in InRouter302 (critical 9.9)
- [CVE-2022-25932](https://insights.sbomify.com/CVE-2022-25932/): Privilege escalation in InRouter302 (high 7.4)
- [CVE-2022-21182](https://insights.sbomify.com/CVE-2022-21182/): Privilege escalation in InRouter302 (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22599 and fix it if it is affected.

What it is: CVE-2023-22599 is a high-severity vulnerability in InHand Networks InRouter 302, published on 12 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22599 in the wild and no public exploit code.

Affected product: InHand Networks InRouter 302. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-22599/ (Markdown: https://insights.sbomify.com/CVE-2023-22599/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-22599
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-22599
- OSV: https://osv.dev/vulnerability/CVE-2023-22599

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-22599/
Summaries are generated and may contain mistakes; the official description above is the record.