Huawei Smartphone 8.0.0.336a(C00) Interface Location improper authorization
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
3.3 | $0-$5k | 0.00 |
A vulnerability was found in Huawei Smartphone 8.0.0.336a(C00) (Smartphone Operating System) and classified as problematic. Affected by this issue is some unknown processing of the component Interface. The manipulation with an unknown input leads to a improper authorization vulnerability (Location). Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality. CVE summarizes:
Huawei smartphones with software Victoria-AL00 8.0.0.336a(C00) have an information leakage vulnerability. Because an interface does not verify authorization correctly, attackers can exploit an application with the authorization of phone state to obtain user location additionally.
The bug was discovered 07/04/2018. The weakness was published 07/31/2018 (Website). The advisory is available at huawei.com. This vulnerability is handled as CVE-2018-7957 since 03/08/2018. The exploitation is known to be easy. Local access is required to approach this attack. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1548.002 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 27 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.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.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
Name: LocationClass: Improper authorization / Location
CWE: CWE-285 / CWE-266
ATT&CK: T1548.002
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/08/2018 🔍07/04/2018 🔍
07/31/2018 🔍
07/31/2018 🔍
08/01/2018 🔍
04/27/2023 🔍
Sources
Vendor: huawei.comAdvisory: sa-20180704-01
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-7957 (🔍)
Entry
Created: 08/01/2018 11:07Updated: 04/27/2023 23:37
Changes: 08/01/2018 11:07 (59), 03/12/2020 09:23 (2), 04/27/2023 23:37 (3)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.