Reyee OS: Use of Inherently Dangerous Function
CVE-2024-52324 is a critical-severity use of inherently dangerous function vulnerability in Reyee OS from Ruijie, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2.320.x as the first without the flaw, so updating Reyee OS to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.69% chance of exploitation within 30 days, higher than 53% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Reyee OS to 2.320.x or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Ruijie | Reyee OS | 2.206.x up to, but not including, 2.320.x | 2.320.x |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.2 | Critical | CNA (hq.dhs.gov) |
| CVSS 3.1 | 9.8 | Critical | CNA (hq.dhs.gov) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Inherently Dangerous Function
The product calls a function that can never be guaranteed to work safely, regardless of how it is used.
How developers prevent this class of flaw
- Identify a list of prohibited API functions and prohibit developers from using these functions, providing safer alternatives. In some cases, automatic code analysis tools or the compiler can be instructed to spot use of prohibited functions, such as the banned.h include file from Microsoft's SDL.
- Use grep or static analysis tools to spot usage of dangerous functions.
More Use of Inherently Dangerous Function vulnerabilities (CWE-242)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/news-events/ics-advisories/icsa-24-338-01Third Party Advisory, US Government Resource
Other vulnerabilities in Reyee OS
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Recent Use of Inherently Dangerous Function vulnerabilities
- 8.8 High severity
Spotted an error? Tell us.