MQTT device impersonation via serial-derived credentials
Published Dec 6, 2024 · Updated Dec 6, 2024
Weak credentials in Ruijie Networks ReyeeOS 2.206.x through versions before 2.320.x allow remote attackers to impersonate MQTT devices. The mqlink.elf cloud client uses the device serial number as the MQTT username and SHA-256 of the reversed serial number as its password. Knowledge or prediction of a serial number is sufficient to authenticate as the device and disconnect it from cloud management.
Summary
What happened
Weak credentials in Ruijie Networks ReyeeOS 2.206.x through versions before 2.320.x allow remote attackers to impersonate MQTT devices. The mqlink.elf cloud client uses the device serial number as the MQTT username and SHA-256 of the reversed serial number as its password. Knowledge or prediction of a serial number is sufficient to authenticate as the device and disconnect it from cloud management.
The record
- CVE
- CVE-2024-45722
- Published
- Dec 6, 2024
- Updated
- Dec 6, 2024
- Vendor
- Ruijie Networks
- Product
- ReyeeOS
- Classifications
- CWE-1391, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 6, 2024CVE publishedPublication date reported by the CVE source.
- Dec 6, 2024Record 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=2.206.x <2.320.x
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.
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