2345 Security Guard 3.7 Driver 2345BdPcSafe.sys input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in 2345 Security Guard 3.7. It has been classified as critical. The impacted element is an unknown function in the library 2345BdPcSafe.sys of the component Driver. This manipulation causes input validation. The identification of this vulnerability is CVE-2018-10976. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability was found in 2345 Security Guard 3.7 (Firewall Software). It has been declared as critical. Affected by this vulnerability is an unknown code block in the library 2345BdPcSafe.sys of the component Driver. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In 2345 Security Guard 3.7, the driver file (2345BdPcSafe.sys, X64 version) allows local users to cause a denial of service (BSOD) or possibly have unspecified other impact because of not validating input values from IOCTL 0x00222050.
The bug was discovered 05/10/2018. The weakness was shared 05/10/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2018-10976 since 05/10/2018. Attacking locally is a requirement. The requirement for exploitation is a single authentication. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-117620, VDB-117618 and VDB-117617 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.2
VulDB Base Score: 6.6
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
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: Input validationCWE: CWE-20
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Timeline
05/10/2018 🔍05/10/2018 🔍
05/10/2018 🔍
05/10/2018 🔍
05/11/2018 🔍
02/04/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-10976 (🔍)
GCVE (CVE): GCVE-0-2018-10976
GCVE (VulDB): GCVE-100-117619
See also: 🔍
Entry
Created: 05/11/2018 11:05Updated: 02/04/2020 14:33
Changes: 05/11/2018 11:05 (59), 02/04/2020 14:33 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.