Google go-tpm TPM1.2 Library up to 0.2.x migrationAuth initialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Google go-tpm TPM1.2 Library up to 0.2.x. This vulnerability affects unknown code. Performing a manipulation of the argument migrationAuth results in initialization. This vulnerability is reported as CVE-2020-8918. The attack requires a local approach. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Google go-tpm TPM1.2 Library up to 0.2.x (Programming Language Software). It has been classified as problematic. This affects an unknown functionality. The manipulation of the argument migrationAuth with an unknown input leads to a initialization vulnerability. CWE is classifying the issue as CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. This is going to have an impact on confidentiality. The summary by CVE is:
An improperly initialized 'migrationAuth' value in Google's go-tpm TPM1.2 library versions prior to 0.3.0 can lead an eavesdropping attacker to discover the auth value for a key created with CreateWrapKey. An attacker listening in on the channel can collect both 'encUsageAuth' and 'encMigrationAuth', and then can calculate 'usageAuth ^ encMigrationAuth' as the 'migrationAuth' can be guessed for all keys created with CreateWrapKey. TPM2.0 is not impacted by this. We recommend updating your library to 0.3.0 or later, or, if you cannot update, to call CreateWrapKey with a random 20-byte value for 'migrationAuth'.
The weakness was disclosed 08/11/2020 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2020-8918 since 02/12/2020. The exploitability is told to be difficult. An attack has to be approached locally. The successful exploitation needs a authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 0.3.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.1
VulDB Base Score: 2.2
VulDB Temp Score: 2.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.3
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: 🔍
Exploiting
Class: InitializationCWE: CWE-665
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
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: go-tpm TPM1.2 Library 0.3.0
Timeline
02/12/2020 🔍08/11/2020 🔍
08/12/2020 🔍
11/08/2020 🔍
Sources
Vendor: google.comAdvisory: github.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-8918 (🔍)
GCVE (CVE): GCVE-0-2020-8918
GCVE (VulDB): GCVE-100-159657
Entry
Created: 08/12/2020 10:37Updated: 11/08/2020 13:25
Changes: 08/12/2020 10:37 (39), 08/12/2020 10:42 (12), 11/08/2020 13:22 (1), 11/08/2020 13:25 (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.