Cyber Resilience

CVE-2024-47791

Ruijienetworks Reyee Os 2.206.0 – 2.320.0

Published
06 December 2024
Modified
10 December 2024
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0039 32th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2024-47791 is a high-severity Improper Neutralization of Wildcards or Matching Symbols (CWE-155) vulnerability in Ruijienetworks Reyee Os. Its CVSS base score is 8.7 (High).

Operationally, ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-155

Related Threats

CVEs Like This One

CVE-2024-45722Same product: Ruijienetworks Reyee Os
CVE-2024-46874Same product: Ruijienetworks Reyee Os
CVE-2024-47146Same product: Ruijienetworks Reyee Os
CVE-2023-53881Same product: Ruijienetworks Reyee Os
CVE-2024-48874Same product: Ruijienetworks Reyee Os
CVE-2024-47547Same product: Ruijienetworks Reyee Os
CVE-2024-47043Same product: Ruijienetworks Reyee Os
CVE-2024-52324Same product: Ruijienetworks Reyee Os
CVE-2024-51727Same product: Ruijienetworks Reyee Os
CVE-2024-42494Same product: Ruijienetworks Reyee Os

Affected Assets

ruijienetworks
reyee os
2.206.0 — 2.320.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation partial match

Input validation directly requires checking and sanitizing special elements such as wildcards before they are passed downstream.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization to block wildcard injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect wildcard issues but does not itself implement neutralization controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and sanitization that directly prevents wildcard injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for neutralizing special characters before downstream processing.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage safe handling of untrusted input but do not prescribe specific wildcard neutralization.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require proper escaping or neutralization of wildcard and matching symbols.

References