PatchSiren cyber security CVE debrief
CVE-2024-42494 Ruijie CVE debrief
Ruijie Reyee OS versions 2.206.x through 2.319.x contain a feature that could allow sub-accounts or attackers to view and exfiltrate sensitive information from all cloud accounts registered to Ruijie's services. The vulnerability was assigned a CVSS 3.1 score of 4.9 (MEDIUM severity). CISA published this advisory on December 3, 2024, with an update on December 10, 2024, that revised CVSS scores. Ruijie reports that the issues have been fixed on the cloud side, and no action is required by end users.
- Vendor
- Ruijie
- Product
- Reyee OS
- CVSS
- MEDIUM 4.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2024-12-03
- Original CVE updated
- 2024-12-10
- Advisory published
- 2024-12-03
- Advisory updated
- 2024-12-10
Who should care
Organizations using Ruijie Reyee OS cloud-managed networking equipment, particularly those with multi-tenant or sub-account configurations.
Technical summary
A feature in Ruijie Reyee OS versions 2.206.x through 2.319.x could enable sub-accounts or attackers to view and exfiltrate sensitive information from all cloud accounts registered to Ruijie's services. The vulnerability requires high privileges (PR:H) but is exploitable over the network with low complexity. Ruijie has implemented cloud-side fixes, and no end-user action is required.
Defensive priority
medium
Recommended defensive actions
- Verify that deployed Ruijie Reyee OS instances are running version 2.320.x or later, or confirm with Ruijie that cloud-side mitigations are active for your environment.
- Review cloud account access logs for unauthorized data access or exfiltration activity during the exposure window.
- Audit sub-account permissions and remove unnecessary access to cloud management functions.
- Apply network segmentation to limit cloud management interface exposure to authorized administrative hosts only.
- Monitor for anomalous API calls or data retrieval patterns from Ruijie cloud services.
Evidence notes
The vulnerability affects Ruijie Reyee OS versions 2.206.x up to but not including 2.320.x. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, indicating network attack vector, low attack complexity, high privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact.
Sources and references
Verified primary and authoritative sources
-
CVE-2024-42494 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2024-42494
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2024-42494 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2024-42494
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source item URL
Unverified legacy reference
URL: https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/OT/white/2024/icsa-24-338-01.json
cisa_csaf
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/news-events/ics-advisories/icsa-24-338-01
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/uscert/ics/alerts/ICS-ALERT-10-301-01
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/resources-tools/resources/ics-recommended-practices
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/sites/default/files/publications/Cybersecurity_Best_Practices_for_Industrial_Control_Systems.pdf
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/topics/industrial-control-systems
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/uscert/sites/default/files/publications/emailscams0905.pdf
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/uscert/ncas/tips/ST04-014
Reference
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.