fan_xpert: Exposed IOCTL with Insufficient Access Control
CVE-2024-30804 is a critical-severity exposed IOCTL with insufficient access control vulnerability in fan_xpert from ASUS, 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 10013 as the first without the flaw, so updating fan_xpert to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.82% chance of exploitation within 30 days, higher than 58% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update fan_xpert to 10013 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
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 CISA (ADP).
Official description
An issue discovered in the DeviceIoControl component in ASUS Fan_Xpert before v.10013 allows an attacker to execute arbitrary code via crafted IOCTL requests.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Exposed IOCTL with Insufficient Access Control
The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.
How developers prevent this class of flaw
- In Windows environments, use proper access control for the associated device or device namespace. See References.
More Exposed IOCTL with Insufficient Access Control vulnerabilities (CWE-782)
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
Other references
Recent Exposed IOCTL with Insufficient Access Control vulnerabilities
- 7.8 High severity
Spotted an error? Tell us.