Skip to main content
CVE-2024-55408VulnerabilityPublished Updated

CVE-2024-55408: ASUS ASCI · Missing Authorization

Affects ASUS ASCISource CVE Database V5

0

Not known to be exploited · CVSS 5.1 Medium : upgrade to 3.1.41.0 or 1.0.30.0 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.1.41.0, 1.0.30.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade ASUS ASCI to 3.1.41.0 or 1.0.30.0.

Affected software

ProductAffectedFixed in
ASUS ASCIAffected
  • <1.0.30.0
  • <3.1.41.0
Fixed in
  • 1.0.30.0
  • 3.1.41.0

AI-suggested

2) Restrict local access to systems running ASUS ASCI software to trusted and authorized personnel only, minimizing the risk of local exploitation. 3) Employ endpoint protection solutions capable of detecting anomalous IOCTL requests or unusual driver interactions. 4) Implement strict user privilege management to limit the number of users with local access and enforce the principle of least privilege. 5) Conduct regular audits of installed drivers and software versions to identify vulnerable instances. 6) Consider deploying application control or driver whitelisting mechanisms to prevent unauthorized or malicious driver usage. 7) Educate system administrators and users about the risks of local exploitation and the importance of physical and logical access controls. These steps go beyond generic advice by focusing on controlling local access and monitoring driver interactions, which are critical given the local attack vector and lack of authentication requirements.

Description

An improper access control vulnerability in the AsusSAIO.sys driver may lead to the misuse of software functionality utilizing the driver when crafted IOCTL requests are supplied.

References

Community reviews

Loading reviews…