| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in ThinkPad Product. The impacted element is an unknown function of the component BIOS Image Handler. The manipulation leads to debug code. This vulnerability is traded as CVE-2020-8320. An attack has to be approached locally. There is no exploit available.
Details
A vulnerability, which was classified as critical, has been found in ThinkPad Product (version now known). This issue affects some unknown processing of the component BIOS Image Handler. The manipulation with an unknown input leads to a debug code vulnerability. Using CWE to declare the problem leads to CWE-489. The product is deployed to unauthorized actors with debugging code still enabled or active, which can create unintended entry points or expose sensitive information. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An internal shell was included in BIOS image in some ThinkPad models that could allow escalation of privilege.
The weakness was shared 06/09/2020. The identification of this vulnerability is CVE-2020-8320 since 01/28/2020. The exploitation is known to be difficult. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 4.9
VulDB Temp Score: 4.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: 🔍
Exploiting
Class: Debug codeCWE: CWE-489
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
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/28/2020 🔍06/09/2020 🔍
06/10/2020 🔍
10/23/2020 🔍
Sources
Status: Not definedCVE: CVE-2020-8320 (🔍)
GCVE (CVE): GCVE-0-2020-8320
GCVE (VulDB): GCVE-100-156449
Entry
Created: 06/10/2020 11:40Updated: 10/23/2020 17:11
Changes: 06/10/2020 11:40 (34), 06/10/2020 11:45 (11), 10/23/2020 17:11 (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.