| 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 declared as problematic. Affected by this issue is some unknown functionality of the component AMI BMC Firmware. Executing a manipulation can lead to weak prng. The identification of this vulnerability is CVE-2020-11616. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic was found in NVIDIA DGX up to 3.38.29. This vulnerability affects some unknown processing of the component AMI BMC Firmware. The manipulation with an unknown input leads to a weak prng vulnerability. The CWE definition for the vulnerability is CWE-338. The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong. As an impact it is known to affect confidentiality.
The weakness was shared 10/29/2020. The advisory is shared for download at nvidia.custhelp.com. This vulnerability was named CVE-2020-11616. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.001.
Upgrading to version 3.38.30 eliminates this vulnerability.
Once again VulDB remains the best source 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: Weak prngCWE: CWE-338 / CWE-331 / CWE-330
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-11616 (🔍)
GCVE (CVE): GCVE-0-2020-11616
GCVE (VulDB): GCVE-100-164044
Entry
Created: 10/29/2020 08:17Updated: 11/30/2020 08:23
Changes: 10/29/2020 08:17 (38), 11/30/2020 08:18 (3), 11/30/2020 08:23 (18)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.