MQTT credential disclosure via predictable MD5 salt
Published Jan 12, 2023 · Updated Jan 16, 2025
Predictable hashing in InHand Networks InRouter 302 before 3.5.56 and InRouter 615 before 2.3.0.r5542 lets remote attackers obtain MQTT credentials. The HTTP/HTTPS response encodes those credentials with MD5 and a hardcoded, predictable salt, allowing the derived value to be calculated. No authentication or user interaction is required, but the cloud-platform request must be spoofed; exposed credentials permit receipt of potentially sensitive MQTT commands and can temporarily disconnect the device.
Summary
What happened
Predictable hashing in InHand Networks InRouter 302 before 3.5.56 and InRouter 615 before 2.3.0.r5542 lets remote attackers obtain MQTT credentials. The HTTP/HTTPS response encodes those credentials with MD5 and a hardcoded, predictable salt, allowing the derived value to be calculated. No authentication or user interaction is required, but the cloud-platform request must be spoofed; exposed credentials permit receipt of potentially sensitive MQTT commands and can temporarily disconnect the device.
The record
- CVE
- CVE-2023-22599
- Published
- Jan 12, 2023
- Updated
- Jan 16, 2025
- Vendor
- InHand Networks
- Product
- InRouter 302
- Classifications
- CWE-760, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2023CVE publishedPublication date reported by the CVE source.
- Jan 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <IR302 V3.5.56
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo