Norman Security Suite 8.0 Malware Detection Product race condition ⚔ [Disputed]
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.4 | $0-$5k | 0.00 |
A vulnerability classified as critical was found in Norman Security Suite 8.0. This vulnerability affects an unknown code block 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 Norman Security Suite PRO 8.0 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 disclosed 05/05/2010 (Website). The advisory is available at theregister.co.uk. This vulnerability was named CVE-2010-5167 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†). The entries VDB-61839, VDB-61838, VDB-61837 and VDB-61836 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.4
VulDB Temp Score: 7.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
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: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/05/2010 🔍05/05/2010 🔍
05/29/2010 🔍
08/25/2012 🔍
08/25/2012 🔍
03/23/2015 🔍
08/07/2024 🔍
Sources
Advisory: theregister.co.ukStatus: Not defined
Disputed: 🔍
CVE: CVE-2010-5167 (🔍)
GCVE (CVE): GCVE-0-2010-5167
GCVE (VulDB): GCVE-100-61822
SecurityFocus: 39924 - Multiple Vendor Argument Switch Security Bypass Vulnerabilities
OSVDB: 67660 - Multiple Security Product Argument Switch Race Condition Scan Bypass
See also: 🔍
Entry
Created: 03/23/2015 04:50 PMUpdated: 08/07/2024 01:35 PM
Changes: 03/23/2015 04:50 PM (53), 08/16/2018 07:27 AM (3), 08/07/2024 01:35 PM (17)
Complete: 🔍
Cache ID: 18:8B4:40
No comments yet. Languages: en.
Please log in to comment.