dbcve.org
Reyee OsOperating system · Ruijienetworks

CVE-2024-52324

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-06
Fix available
A fix is available. Upgrade to 2.320.0 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
Ruijie Reyee OS versions 2.206.x up to but not including 2.320.x uses an inherently dangerous function which could allow an attacker to send a malicious MQTT message resulting in devices executing arbitrary OS commands.

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

Ruijie Reyee OS versions 2.206.x through 2.319.x contain a command injection vulnerability where the system improperly handles MQTT messages, allowing an attacker to execute arbitrary OS commands by sending specially crafted MQTT payloads due to use of a dangerous function (likely system() or similar).

MitigationUpgrade Ruijie Reyee OS to version 2.320.x or later. If immediate patching is not possible, implement network segmentation to restrict MQTT traffic access and block untrusted sources from reaching the device management network.

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
Reyee OsOperating system
Affected:>= 2.206.0, < 2.320.0

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 installed Ruijie Reyee OS version
    Access the device web interface or CLI and retrieve the OS firmware version. In CLI, this is typically shown via 'show version' or 'show system-info'. On the web GUI, check under 'System' > 'Device Management' or similar status pages.
    Affected if The installed version falls within the range 2.206.0 through 2.319.x (versions greater than or equal to 2.206.0 but less than 2.320.0).
  2. Confirm the MQTT service is enabled on the device
    Check the device configuration for MQTT settings. In the Reyee OS web interface, look under 'Advanced' > 'MQTT' or 'System' > 'Services'. In CLI, use 'show mqtt status' or review the running configuration.
    Affected if MQTT service is explicitly enabled on the device, as the vulnerability requires MQTT to be active for exploitation.
  3. Identify network exposure of the MQTT service
    Determine if the device MQTT port (default 1883) is listening on any externally accessible interface. Use 'netstat -an | grep 1883' or review firewall rules. Check if the management interface is bound to WAN or an untrusted VLAN.
    Affected if The MQTT service is reachable from untrusted networks, interfaces, or VLANs rather than being isolated to a trusted management network.
  4. Verify network segmentation controls
    Review network infrastructure to determine if the device management network is properly segmented. Check ACLs, firewall rules, or VLAN configuration that controls access to the device's management IP and MQTT port.
    Affected if No network segmentation or access controls exist to restrict MQTT traffic to trusted management systems only, leaving the service exposed to potential attackers.

The environment is affected if the installed Ruijie Reyee OS version is 2.206.0 through 2.319.x AND the MQTT service is enabled and accessible from any network where untrusted sources could reach the device.

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.320.0 or later
Fixed in 2.320.0
Interim mitigation

Upgrade Ruijie Reyee OS to version 2.320.x or later. If immediate patching is not possible, implement network segmentation to restrict MQTT traffic access and block untrusted sources from reaching the device management network.

Recommended fix High confidence

Ruijie Reyee OS version 2.320.0 or later

  1. Inventory all Ruijie Reyee OS devices in the environment
  2. Check the current firmware version on each device (likely via web UI or CLI)
  3. Identify devices running version 2.206.0 through 2.31x.x (versions < 2.320.0)
  4. Obtain the fixed firmware version 2.320.0 or later from the official Ruijie support portal
  5. Review vendor upgrade documentation and create a rollback plan
  6. Apply the firmware upgrade to affected devices via the vendor-recommended method (web UI, CLI, or cloud management)
  7. After upgrade, verify each device is running version 2.320.0 or later
  8. Confirm the MQTT service is no longer vulnerable to command injection

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

Fix this in Reyee Os Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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