GEAR Product GEARAspiWDM.sys Blue Screen race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in GEAR Product. This vulnerability affects unknown code in the library GEARAspiWDM.sys. Performing a manipulation results in race condition (Blue Screen). This vulnerability is known as CVE-2018-15499. Attacking locally is a requirement. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in GEAR Product (the affected version is unknown). It has been classified as critical. This affects an unknown code in the library GEARAspiWDM.sys. The manipulation with an unknown input leads to a race condition vulnerability (Blue Screen). 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 availability. The summary by CVE is:
GEAR Software products that include GEARAspiWDM.sys, 2.2.5.0, allow local users to cause a denial of service (Race Condition and BSoD on Windows) by not checking that user-mode memory is available right before writing to it. A check is only performed at the beginning of a long subroutine.
The bug was discovered 08/23/2018. The weakness was published 08/24/2018 (Website). The advisory is shared at downwithup.github.io. This vulnerability is uniquely identified as CVE-2018-15499 since 08/17/2018. An attack has to be approached locally. A authentication is needed for exploitation. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
Upgrading eliminates this vulnerability.
Similar entries are available at VDB-124489, VDB-124490, VDB-124491 and VDB-125805. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.1VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.7
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
Name: Blue ScreenClass: Race condition / Blue Screen
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
08/17/2018 🔍08/23/2018 🔍
08/24/2018 🔍
08/24/2018 🔍
08/25/2018 🔍
03/18/2020 🔍
Sources
Advisory: downwithup.github.ioStatus: Not defined
CVE: CVE-2018-15499 (🔍)
GCVE (CVE): GCVE-0-2018-15499
GCVE (VulDB): GCVE-100-123225
See also: 🔍
Entry
Created: 08/25/2018 08:26Updated: 03/18/2020 08:35
Changes: 08/25/2018 08:26 (59), 03/18/2020 08:35 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.