| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in NVIDIA DGX up to 3.38.29. It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the component Cipher Key Handler. Performing a manipulation results in hard-coded key. This vulnerability was named CVE-2020-11615. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in NVIDIA DGX up to 3.38.29. This affects an unknown code block of the component Cipher Key Handler. The manipulation with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality.
The weakness was presented 10/29/2020. It is possible to read the advisory at nvidia.custhelp.com. This vulnerability is uniquely identified as CVE-2020-11615. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.
Upgrading to version 3.38.30 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 3.38.0
- 3.38.1
- 3.38.2
- 3.38.3
- 3.38.4
- 3.38.5
- 3.38.6
- 3.38.7
- 3.38.8
- 3.38.9
- 3.38.10
- 3.38.11
- 3.38.12
- 3.38.13
- 3.38.14
- 3.38.15
- 3.38.16
- 3.38.17
- 3.38.18
- 3.38.19
- 3.38.20
- 3.38.21
- 3.38.22
- 3.38.23
- 3.38.24
- 3.38.25
- 3.38.26
- 3.38.27
- 3.38.28
- 3.38.29
License
Website
- Vendor: https://www.nvidia.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Hard-coded keyCWE: CWE-321 / CWE-320
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: 🔍
Upgrade: DGX 3.38.30
Timeline
04/07/2020 🔍10/29/2020 🔍
10/29/2020 🔍
11/30/2020 🔍
Sources
Vendor: nvidia.comAdvisory: nvidia.custhelp.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-11615 (🔍)
GCVE (CVE): GCVE-0-2020-11615
GCVE (VulDB): GCVE-100-164043
Entry
Created: 10/29/2020 08:16Updated: 11/30/2020 08:13
Changes: 10/29/2020 08:16 (38), 11/30/2020 08:07 (3), 11/30/2020 08:13 (18)
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.