Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-9337: CWE-476 NULL Pointer Dereference in ASUS Armoury Crate

0
Medium
VulnerabilityCVE-2025-9337cvecve-2025-9337cwe-476
Published: Mon Oct 13 2025 (10/13/2025, 09:24:35 UTC)
Source: CVE Database V5
Vendor/Project: ASUS
Product: Armoury Crate

Description

A null pointer dereference has been identified in the AsIO3.sys driver. The vulnerability can be triggered by a specially crafted input, which may lead to a system crash (BSOD). Refer to the 'Security Update for Armoury Crate App' section on the ASUS Security Advisory for more information.

AI-Powered Analysis

AILast updated: 10/21/2025, 20:40:33 UTC

Technical Analysis

CVE-2025-9337 is a vulnerability identified in the AsIO3.sys driver component of ASUS Armoury Crate software, a utility commonly pre-installed on ASUS devices to manage hardware settings and system performance. The vulnerability is classified as a NULL pointer dereference (CWE-476), which occurs when the driver attempts to access memory through a pointer that has not been properly initialized or has been set to NULL. This flaw can be triggered by sending a specially crafted input to the driver, causing it to dereference the NULL pointer and subsequently crash the system, resulting in a Blue Screen of Death (BSOD). The vulnerability affects Armoury Crate versions prior to 6.3.4. According to the CVSS v4.0 vector (AV:L/AC:L/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N), the attack requires local access with low privileges but no user interaction, and it does not compromise confidentiality or integrity, only availability. The scope is limited to the local system, and no known exploits have been reported in the wild as of the publication date. This vulnerability can be leveraged by an attacker with limited access to cause denial of service, potentially disrupting critical operations or user productivity. The lack of authentication requirement and ease of triggering the flaw with crafted input makes it a concern for environments where multiple users or processes have local access to affected machines. ASUS has acknowledged the issue and recommends updating to version 6.3.4 or later, though no patch links were provided at the time of this report.

Potential Impact

The primary impact of CVE-2025-9337 on European organizations is denial of service due to system crashes caused by the NULL pointer dereference in the Armoury Crate driver. This can disrupt business operations, especially in environments where ASUS hardware is widely deployed and Armoury Crate is used for system management, such as in corporate offices, gaming centers, or development labs. The vulnerability does not expose sensitive data or allow privilege escalation, but repeated crashes could lead to productivity losses, potential data corruption if crashes occur during critical operations, and increased support costs. Organizations with strict uptime requirements or those using ASUS devices in critical infrastructure or industrial control systems may face operational risks. Since the attack vector requires local access with low privileges, insider threats or malware with limited user rights could exploit this vulnerability to cause disruption. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits after public disclosure. European entities should prioritize patching to maintain system stability and prevent potential denial of service scenarios.

Mitigation Recommendations

To mitigate CVE-2025-9337, European organizations should: 1) Immediately inventory all ASUS devices running Armoury Crate and identify versions prior to 6.3.4. 2) Apply the official update to Armoury Crate version 6.3.4 or later as soon as it becomes available from ASUS, ensuring the AsIO3.sys driver is updated. 3) Restrict local access to systems with Armoury Crate installed, limiting user privileges to reduce the risk of exploitation by low-privilege users. 4) Monitor system logs and crash reports for signs of unexplained BSODs that could indicate attempted exploitation. 5) Implement endpoint protection solutions that can detect abnormal driver behavior or attempts to send crafted inputs to kernel drivers. 6) Educate users about the risks of running untrusted software locally, as local access is required for exploitation. 7) Coordinate with IT asset management to ensure timely deployment of updates and maintain an up-to-date inventory of affected devices. 8) Consider network segmentation to isolate critical systems running ASUS hardware to limit lateral movement in case of compromise. These steps go beyond generic advice by focusing on access control, monitoring, and proactive patch management tailored to the specific vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
ASUS
Date Reserved
2025-08-22T02:50:58.939Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68ecc911ff270e1f1a069210

Added to database: 10/13/2025, 9:40:33 AM

Last enriched: 10/21/2025, 8:40:33 PM

Last updated: 12/3/2025, 6:27:15 AM

Views: 73

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats