Asus SABERTOOTH X99 Driver 1.0.1.0 IOCTL Request AsIO64.sys exposed ioctl with insufficient access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.5$0-$5k0.00

Summaryinfo

A vulnerability was found in Asus SABERTOOTH X99 Driver 1.0.1.0. It has been classified as problematic. Affected is an unknown function in the library AsIO64.sys of the component IOCTL Request Handler. Performing a manipulation results in an unknown weakness. This vulnerability is known as CVE-2024-33219. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Asus SABERTOOTH X99 Driver 1.0.1.0. This affects an unknown code block in the library AsIO64.sys of the component IOCTL Request Handler. CWE is classifying the issue as CWE-782. The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL. The impact remains unknown. The summary by CVE is:

An issue in the component AsIO64.sys of ASUSTeK Computer Inc ASUS SABERTOOTH X99 Driver v1.0.1.0 allows attackers to escalate privileges and execute arbitrary code via sending crafted IOCTL requests.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-33219 since 04/23/2024. Technical details of the vulnerability are known, but there is no available exploit.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.6
VulDB Meta Temp Score: 6.5

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 7.8
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Exposed ioctl with insufficient access control
CWE: CWE-782
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/23/2024 🔍
05/22/2024 +29 days 🔍
05/22/2024 +0 days 🔍
08/20/2024 +90 days 🔍

Sourcesinfo

Vendor: asus.com

Advisory: github.com
Status: Not defined

CVE: CVE-2024-33219 (🔍)
GCVE (CVE): GCVE-0-2024-33219
GCVE (VulDB): GCVE-100-265935

Entryinfo

Created: 05/22/2024 18:43
Updated: 08/20/2024 20:30
Changes: 05/22/2024 18:43 (52), 08/20/2024 20:30 (13)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!