Cyber Resilience

CVE-2024-51727

Ruijienetworks Reyee Os 2.206.0 – 2.320.0

Published
06 December 2024
Modified
10 December 2024
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/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.0051 41th percentile
Risk Priority 36 floored blend · peak EPSS

Summary

CVE-2024-51727 is a high-severity Premature Release of Resource During Expected Lifetime (CWE-826) vulnerability in Ruijienetworks Reyee Os. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 41th 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 SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — 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 contains a feature that could enable attackers to invalidate a legitimate user's session and cause a denial-of-service attack on a user's account.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-52324Same product: Ruijienetworks Reyee Os
CVE-2024-48874Same product: Ruijienetworks Reyee Os
CVE-2024-45722Same product: Ruijienetworks Reyee Os
CVE-2024-47791Same product: Ruijienetworks Reyee Os
CVE-2024-46874Same product: Ruijienetworks Reyee Os
CVE-2023-53881Same product: Ruijienetworks Reyee Os
CVE-2024-47547Same product: Ruijienetworks Reyee Os
CVE-2024-47043Same product: Ruijienetworks Reyee Os
CVE-2024-47146Same 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

Developer testing and evaluation can discover premature-release defects before deployment.

Engineering principles can require correct resource lifetime management so the premature-release pattern is never coded.

Process isolation confines the blast radius when a resource is released while still referenced inside another domain.

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 development practices directly address coding errors that release resources while they are still needed.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover instances of premature resource release after code is deployed.

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.

finds

Security testing can detect premature-release bugs, providing partial mitigation.

prevents

Secure development lifecycle practices can include resource-lifetime checks that reduce premature-release defects.

prevents

Application security requirements can mandate explicit resource-release rules, partially addressing the weakness.

prevents

Secure architecture principles encourage proper resource scoping and lifetime management.

prevents

Secure coding standards directly prohibit premature resource release, covering most of the weakness.

none

Change-management processes may catch resource-handling regressions but do not directly prevent the weakness.

References