CVE-2024-47791: Ruijie Reyee OS Improper Neutralization of Wildcards or Matching Symbols
Published Dec 6, 2024
·Updated
Ruijie Reyee OS versions 2.206.x up to but not including 2.320.x could allow an attacker to subscribe to partial possible topics in Ruijie MQTT broker, and receive partial messages being sent to and from devices.
Affected Software
2 affected components
: Ruijie Reyee OS: Versions 2.206.x up to but not including 2.320.x
Ruijienetworks Reyee Os>=2.206.0<2.320.0
Remediation
Information
Ruijie reports that the issues have been fixed on the cloud and no action is needed by end users. However, CISA recommends users take defensive measures to minimize the risk of exploitation of these vulnerabilities, such as:
* Minimize network exposure for all control system devices and/or systems, ensuring they are not accessible from the internet https://www.cisa.gov/uscert/ics/alerts/ICS-ALERT-10-301-01 .
* Locate control system networks and remote devices behind firewalls and isolating them from business networks.
* When remote access is required, use more secure methods, such as Virtual Private Networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as the connected devices.
Event History
Dec 6, 2024
CVE Published
via MITRE·06:16 PM
Data Sourced
via MITRE·06:16 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2024-47791?
CVE-2024-47791 has a critical severity level due to the potential for unauthorized access to MQTT broker messages.
2
How do I fix CVE-2024-47791?
To mitigate CVE-2024-47791, upgrade Ruijie Reyee OS to version 2.320.x or later.
3
What systems are affected by CVE-2024-47791?
CVE-2024-47791 affects Ruijie Reyee OS versions 2.206.x up to but not including 2.320.x.
4
What potential impact does CVE-2024-47791 have?
CVE-2024-47791 could allow an attacker to subscribe to partial MQTT topics and intercept messages between devices.
5
Is there a workaround for CVE-2024-47791?
Currently, the recommended action for CVE-2024-47791 is to update the software, as no official workaround has been provided.