NVIDIA Windows GPU Display Driver Kernel Mode Layer nvlddmkm.sys denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in NVIDIA Windows GPU Display Driver. It has been rated as problematic. This vulnerability affects unknown code in the library nvlddmkm.sys of the component Kernel Mode Layer. This manipulation causes denial of service. This vulnerability appears as CVE-2020-5982. The attack requires local access. There is no available exploit.
Details
A vulnerability classified as problematic was found in NVIDIA Windows GPU Display Driver (Hardware Driver Software) (version unknown). Affected by this vulnerability is an unknown function in the library nvlddmkm.sys of the component Kernel Mode Layer. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
NVIDIA Windows GPU Display Driver, all versions, contains a vulnerability in the kernel mode layer (nvlddmkm.sys) scheduler, in which the software does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests, which may lead to denial of service.
The weakness was presented 10/02/2020 (Website). The advisory is shared at nvidia.custhelp.com. This vulnerability is known as CVE-2020-5982 since 01/07/2020. An attack has to be approached locally. The successful exploitation requires a single authentication. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-162250, VDB-162251, VDB-162252 and VDB-162254 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.nvidia.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.8
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.4
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: Denial of serviceCWE: CWE-404
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: 🔍
0-Day Time: 🔍
Timeline
01/07/2020 🔍10/02/2020 🔍
10/03/2020 🔍
11/16/2020 🔍
Sources
Vendor: nvidia.comAdvisory: nvidia.custhelp.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-5982 (🔍)
GCVE (CVE): GCVE-0-2020-5982
GCVE (VulDB): GCVE-100-162253
See also: 🔍
Entry
Created: 10/03/2020 06:38Updated: 11/16/2020 11:21
Changes: 10/03/2020 06:38 (37), 10/03/2020 06:43 (4), 11/15/2020 10:18 (4), 11/16/2020 11:17 (1), 11/16/2020 11:21 (14)
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.