eEye Blink 4.6.1 Malware Detection Product race condition ⚔ [Disputed]

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.
7.4	$0-$5k	0.00

Summaryinfo

A vulnerability classified as problematic was found in eEye Blink 4.6.1. Affected by this issue is some unknown functionality of the component Malware Detection. Executing a manipulation of the argument Product can lead to race condition. This vulnerability is registered as CVE-2010-5155. No exploit is available. It is still unclear if this vulnerability genuinely exists.

Detailsinfo

A vulnerability was found in eEye Blink 4.6.1. It has been declared as critical. This vulnerability affects an unknown function of the component Malware Detection. The manipulation of the argument Product with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

** DISPUTED ** Race condition in Blink Professional 4.6.1 on Windows XP allows local users to bypass kernel-mode hook handlers, and execute dangerous code that would otherwise be blocked by a handler but not blocked by signature-based malware detection, via certain user-space memory changes during hook-handler execution, aka an argument-switch attack or a KHOBE attack. NOTE: this issue is disputed by some third parties because it is a flaw in a protection mechanism for situations where a crafted program has already begun to execute.

The weakness was published 05/05/2010 (Website). The advisory is available at theregister.co.uk. This vulnerability was named CVE-2010-5155 since 08/25/2012. The exploitation appears to be difficult. Local access is required to approach this attack. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit.

The real existence of this vulnerability is still doubted at the moment.

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 databases at SecurityFocus (BID 39924†) and OSVDB (67660†). Similar entries are available at VDB-61839, VDB-61838, VDB-61837 and VDB-61836. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• eEye

Name

• Blink

Version

• 4.6.1

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.4
VulDB Meta Temp Score: 7.4

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

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/05/2010 🔍
05/05/2010 +0 days 🔍
05/29/2010 +24 days 🔍
08/25/2012 +818 days 🔍
08/25/2012 +0 days 🔍
03/23/2015 +940 days 🔍
08/07/2024 +3425 days 🔍

Sourcesinfo

Advisory: theregister.co.uk
Status: Not defined
Disputed: 🔍

CVE: CVE-2010-5155 (🔍)
GCVE (CVE): GCVE-0-2010-5155
GCVE (VulDB): GCVE-100-61810
SecurityFocus: 39924 - Multiple Vendor Argument Switch Security Bypass Vulnerabilities
OSVDB: 67660 - Multiple Security Product Argument Switch Race Condition Scan Bypass

See also: 🔍

Entryinfo

Created: 03/23/2015 16:50
Updated: 08/07/2024 06:23
Changes: 03/23/2015 16:50 (53), 02/19/2019 19:56 (3), 08/07/2024 06:23 (17)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

Do you need the next level of professionalism?

Upgrade your account now!