Binalyze up to 3.11.0 IREC.sys fun_1400084d0 Local Privilege Escalation

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

Summaryinfo

A vulnerability identified as problematic has been detected in Binalyze up to 3.11.0. This affects the function fun_1400084d0 in the library IREC.sys. This manipulation causes an unknown weakness. This vulnerability is handled as CVE-2023-41444. It is possible to launch the attack on the local host. Additionally, an exploit exists.

Detailsinfo

A vulnerability has been found in Binalyze up to 3.11.0 and classified as problematic. Affected by this vulnerability is the function fun_1400084d0 in the library IREC.sys. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An issue in Binalyze IREC.sys v.3.11.0 and before allows a local attacker to execute arbitrary code and escalate privileges via the fun_1400084d0 function in IREC.sys driver.

The weakness was released 09/28/2023. The advisory is shared at blog.dru1d.ninja. This vulnerability is known as CVE-2023-41444 since 08/30/2023. Technical details and also a public exploit are known.

It is possible to download the exploit at blog.dru1d.ninja. It is declared as proof-of-concept.

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

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-45944). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.3

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

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Local Privilege Escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

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

08/30/2023 🔍
09/28/2023 +29 days 🔍
09/28/2023 +0 days 🔍
02/01/2026 +857 days 🔍

Sourcesinfo

Advisory: blog.dru1d.ninja
Status: Not defined

CVE: CVE-2023-41444 (🔍)
GCVE (CVE): GCVE-0-2023-41444
GCVE (VulDB): GCVE-100-240781
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 09/28/2023 07:44
Updated: 02/01/2026 09:29
Changes: 09/28/2023 07:44 (39), 10/21/2023 14:10 (11), 09/23/2024 22:47 (15), 02/01/2026 09:29 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!