|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.
A vulnerability, which was classified as problematic, has been found in Xiaomi MIX 2 4.4.78. Affected by this issue is an unknown part of the file /dev/elliptic1. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-476. Impacted is availability. CVE summarizes:
On Xiaomi MIX 2 devices with the 4.4.78 kernel, a NULL pointer dereference in the ioctl interface of the device file /dev/elliptic1 or /dev/elliptic0 causes a system crash via IOCTL 0x4008c575 (aka decimal 1074316661).
The bug was discovered 01/07/2019. The weakness was disclosed 02/17/2019. This vulnerability is handled as CVE-2019-8413 since 02/17/2019. The exploitation is known to be easy. The attack needs to be approached locally. No form of authentication is required for exploitation. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 41 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
CVSSv3VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
ExploitingClass: Denial of service
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
Threat IntelligenceThreat: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔍
02/17/2019 +41 days 🔍
02/17/2019 +0 days 🔍
02/18/2019 +1 days 🔍
05/11/2020 +448 days 🔍
SourcesStatus: Not defined
CVE: CVE-2019-8413 (🔍)
EntryCreated: 02/18/2019 09:37 AM
Updated: 05/11/2020 06:48 AM
Changes: (1) vulnerability_discoverydate
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!