MSI Afterburner 4.6.5.16370 IOCTL RTCore64.sys null pointer dereference

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.
4.4$0-$5k0.00

Summaryinfo

A vulnerability was found in MSI Afterburner 4.6.5.16370 and classified as critical. Affected is an unknown function in the library RTCore64.sys of the component IOCTL Handler. Such manipulation leads to null pointer dereference. This vulnerability is referenced as CVE-2024-1443. The attack can only be performed from a local environment. No exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in MSI Afterburner 4.6.5.16370. Affected by this issue is an unknown code in the library RTCore64.sys of the component IOCTL Handler. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. CVE summarizes:

MSI Afterburner v4.6.5.16370 is vulnerable to a Denial of Service vulnerability by triggering the 0x80002000 IOCTL code of the RTCore64.sys driver. The handle to the driver can only be obtained from a high integrity process.

The weakness was published 03/07/2024. The advisory is shared for download at fluidattacks.com. This vulnerability is handled as CVE-2024-1443 since 02/12/2024. There are known technical details, but no exploit is available.

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

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.4

VulDB Base Score: 4.4
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 4.4
CNA Vector (Fluid Attacks): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

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

02/12/2024 🔍
03/07/2024 +24 days 🔍
03/07/2024 +0 days 🔍
10/15/2025 +587 days 🔍

Sourcesinfo

Advisory: fluidattacks.com
Status: Not defined

CVE: CVE-2024-1443 (🔍)
GCVE (CVE): GCVE-0-2024-1443
GCVE (VulDB): GCVE-100-255980

Entryinfo

Created: 03/07/2024 07:18
Updated: 10/15/2025 02:49
Changes: 03/07/2024 07:18 (49), 10/15/2025 02:49 (16)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!