CVE-2024-45722
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 · uneditedRuijie Reyee OS versions 2.206.x up to but not including 2.320.x uses weak credential mechanism that could allow an attacker to easily calculate MQTT credentials.
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 confidenceRuijie Reyee OS versions 2.206.x through 2.319.x contains a weak credential generation mechanism for MQTT communications that allows attackers to easily calculate valid credentials. The flaw enables unauthorized access to the MQTT broker, potentially exposing sensitive network communications and allowing further compromise of the network infrastructure.
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>= 2.206.0, < 2.320.0CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Ruijie Reyee OS versionLog into the Ruijie router or switch management interface and navigate to System Status or About page to view the firmware version. Alternatively, use CLI command 'show version' or check the system information page.Affected if The displayed version falls within the range >= 2.206.0 and < 2.320.0, placing it in the affected version band.
-
Verify MQTT service statusCheck if MQTT is enabled on the device. This can be done through the web management interface under Network Settings, Services, or IoT configuration sections. In CLI, look for 'mqtt' in the running configuration or use 'show mqtt status' if available.Affected if MQTT service is actively enabled and configured on the device, making the weak credential generation mechanism relevant.
-
Inspect MQTT broker configurationReview the MQTT broker settings to confirm the device is acting as an MQTT broker or publisher. Look for MQTT port (typically 1883 or 8883 for TLS), client credentials, and broker IP/hostname settings in the device configuration.Affected if The device is configured as an MQTT broker or client with credentials generated by the system, exposing the weak credential mechanism.
-
Confirm network exposure of MQTT portCheck firewall rules, port forwarding settings, or network access control lists to determine if MQTT ports (1883/8883) are accessible from untrusted networks or the internet. Use port scanning or check the device's security policies.Affected if MQTT service ports are reachable from outside the trusted network, increasing the risk that weak credentials can be exploited.
The environment is affected if Ruijie Reyee OS version is 2.206.0 through 2.319.x and MQTT service is enabled, as the weak credential generation mechanism applies to MQTT communications.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.320.0
Upgrade Ruijie Reyee OS to version 2.320.x or later to obtain the fixed credential mechanism. If immediate patching is not possible, restrict MQTT port access through network segmentation and monitor for unauthorized MQTT connections.
Reyee OS 2.320.0 or later
- 1. Identify the current Reyee OS version running on the affected device
- 2. Navigate to the device management interface and verify the installed version
- 3. If the version is >= 2.206.0 and < 2.320.0, the device is vulnerable
- 4. Download Reyee OS version 2.320.0 or later from the official Ruijie support portal
- 5. Follow the vendor's standard firmware upgrade procedure to apply the update
- 6. After upgrade, verify the new version is 2.320.0 or higher
- 7. Confirm the MQTT credentials have been regenerated with the stronger mechanism
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45722 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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