VDB-61833 · CVE-2010-5178 · BID 39924

PC Tools ThreatFire 4.7.0.17 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-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in PC Tools ThreatFire 4.7.0.17. This affects an unknown part of the component Malware Detection. Performing a manipulation of the argument Product results in race condition. This vulnerability was named CVE-2010-5178. There is no available exploit. The existence of this vulnerability is still disputed at present.

Detailsinfo

A vulnerability, which was classified as critical, was found in PC Tools ThreatFire 4.7.0.17. This affects some unknown functionality of the component Malware Detection. The manipulation of the argument Product with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

** DISPUTED ** Race condition in ThreatFire 4.7.0.17 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 presented 05/05/2010 (Website). The advisory is shared at theregister.co.uk. This vulnerability is uniquely identified as CVE-2010-5178 since 08/25/2012. The exploitability is told to be difficult. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.

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†). See VDB-61839, VDB-61838, VDB-61837 and VDB-61836 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

Version

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

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

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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

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 🔍
02/19/2019 +1429 days 🔍

Sourcesinfo

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

CVE: CVE-2010-5178 (🔍)
GCVE (CVE): GCVE-0-2010-5178
GCVE (VulDB): GCVE-100-61833
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: 02/19/2019 19:57
Changes: 03/23/2015 16:50 (53), 02/19/2019 19:57 (3)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!