Core Security Technologies CORE FORCE up to 0.95.166 Hook memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Core Security Technologies CORE FORCE up to 0.95.166. This vulnerability affects unknown code of the component Hook Handler. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2008-0366. Moreover, an exploit is present. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Core Security Technologies CORE FORCE up to 0.95.166. This issue affects some unknown functionality of the component Hook Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
CORE FORCE before 0.95.172 does not properly validate arguments to SSDT hook handler functions in the Registry module, which allows local users to cause a denial of service (system crash) and possibly execute arbitrary code in the kernel context via crafted arguments.
The weakness was disclosed 01/18/2008 by Basti (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2008-0366 since 01/18/2008. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.
The exploit is available at securityfocus.com. It is declared as proof-of-concept.
Upgrading to version 0.95.167 eliminates this vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 27341†) and SecurityTracker (ID 1019245†). The entry VDB-40636 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 8.4
VulDB Base Score: 9.3
VulDB Temp Score: 8.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: Memory corruptionCWE: CWE-119
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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: CORE FORCE 0.95.167
Timeline
01/17/2008 🔍01/18/2008 🔍
01/18/2008 🔍
01/18/2008 🔍
01/18/2008 🔍
03/16/2015 🔍
03/26/2019 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Basti
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2008-0366 (🔍)
GCVE (CVE): GCVE-0-2008-0366
GCVE (VulDB): GCVE-100-40637
SecurityFocus: 27341 - CORE FORCE Firewall and Registry Modules Multiple Local Kernel Buffer Overflow Vulnerabilities
SecurityTracker: 1019245
Vupen: ADV-2008-0242
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/16/2015 13:43Updated: 03/26/2019 21:36
Changes: 03/16/2015 13:43 (61), 03/26/2019 21:36 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.