NVIDIA Linux for Tegra up to R28.2 Secure Shell key management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in NVIDIA Linux for Tegra up to R28.2 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Secure Shell. Performing a manipulation results in key management. This vulnerability was named CVE-2019-5672. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in NVIDIA Linux for Tegra up to R28.2. This affects an unknown part of the component Secure Shell. The manipulation with an unknown input leads to a key management vulnerability. CWE is classifying the issue as CWE-320. This is going to have an impact on confidentiality. The summary by CVE is:
NVIDIA Linux for Tegra (L4T) contains a vulnerability where the Secure Shell (SSH) keys provided in the sample rootfs are not replaced by unique host keys after sample rootsfs generation and flashing, which may lead to information disclosure. The updates apply to all versions prior to and including R28.3.
The bug was discovered 04/02/2019. The weakness was presented 04/11/2019 (Website). The advisory is shared at nvidia.custhelp.com. This vulnerability is uniquely identified as CVE-2019-5672 since 01/07/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 9 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version R28.3 eliminates this vulnerability.
See VDB-99310, VDB-109409, VDB-130874 and VDB-130875 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.nvidia.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
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: Key managementCWE: 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: Linux for Tegra R28.3
Timeline
01/07/2019 🔍04/02/2019 🔍
04/11/2019 🔍
04/11/2019 🔍
05/29/2020 🔍
Sources
Vendor: nvidia.comAdvisory: nvidia.custhelp.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-5672 (🔍)
GCVE (CVE): GCVE-0-2019-5672
GCVE (VulDB): GCVE-100-133353
See also: 🔍
Entry
Created: 04/11/2019 21:09Updated: 05/29/2020 09:52
Changes: 04/11/2019 21:09 (58), 05/29/2020 09:52 (2)
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.