CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
3.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Huawei Smartphone. Affected is an unknown function of the component Configuration. The manipulation leads to information disclosure. This vulnerability is traded as CVE-2018-7946. It is possible to launch the attack on the physical device. There is no exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in Huawei Smartphone (Smartphone Operating System) (affected version not known). It has been rated as problematic. This issue affects some unknown functionality of the component Configuration. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
There is an information leak vulnerability in some Huawei smartphones. An attacker may do some specific configuration in the smartphone and trick a user into inputting some sensitive information. Due to improper design, successful exploit may cause some information leak.
The bug was discovered 11/20/2018. The weakness was released 11/27/2018 (Website). The advisory is shared at huawei.com. The identification of this vulnerability is CVE-2018-7946 since 03/09/2018. An attack has to be approached locally. A simple authentication is required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 7 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.2VulDB Meta Temp Score: 3.2
VulDB Base Score: 2.1
VulDB Temp Score: 2.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
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
03/09/2018 🔍11/20/2018 🔍
11/27/2018 🔍
11/27/2018 🔍
11/28/2018 🔍
06/11/2023 🔍
Sources
Vendor: huawei.comAdvisory: sa-20181121-01
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-7946 (🔍)
GCVE (CVE): GCVE-0-2018-7946
GCVE (VulDB): GCVE-100-127241
Entry
Created: 11/28/2018 10:54 AMUpdated: 06/11/2023 05:54 PM
Changes: 11/28/2018 10:54 AM (56), 04/15/2020 05:42 PM (2), 06/11/2023 05:54 PM (2)
Complete: 🔍
Cache ID: 18:A10:40
No comments yet. Languages: en.
Please log in to comment.