AMD Extension to Linux hwmon Service Linux-based Running Average Power Limit Interface routine

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.7$0-$5k0.00

Summaryinfo

A vulnerability was found in AMD Extension to Linux hwmon Service. It has been rated as problematic. The affected element is an unknown function of the component Linux-based Running Average Power Limit Interface. The manipulation leads to routine. This vulnerability is referenced as CVE-2020-12912. It is possible to launch the attack on the physical device. No exploit is available.

Detailsinfo

A vulnerability was found in AMD Extension to Linux hwmon Service (version unknown) and classified as problematic. This issue affects an unknown function of the component Linux-based Running Average Power Limit Interface. The manipulation with an unknown input leads to a routine vulnerability. Using CWE to declare the problem leads to CWE-749. The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted. Impacted is confidentiality.

The weakness was published 11/13/2020. The advisory is shared at amd.com. The identification of this vulnerability is CVE-2020-12912. 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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.7
VulDB Meta Temp Score: 3.7

VulDB Base Score: 2.0
VulDB Temp Score: 2.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Routine
CWE: CWE-749
CAPEC: 🔍
ATT&CK: 🔍

Physical: Yes
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/15/2020 🔍
11/13/2020 +182 days 🔍
11/13/2020 +0 days 🔍
12/06/2020 +23 days 🔍

Sourcesinfo

Advisory: amd.com
Status: Confirmed

CVE: CVE-2020-12912 (🔍)
GCVE (CVE): GCVE-0-2020-12912
GCVE (VulDB): GCVE-100-164885

Entryinfo

Created: 11/13/2020 07:18
Updated: 12/06/2020 20:57
Changes: 11/13/2020 07:18 (35), 12/06/2020 20:52 (2), 12/06/2020 20:57 (18)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!