| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Huawei P8. This vulnerability affects unknown code of the component HiFi Driver. Performing a manipulation results in null pointer dereference. This vulnerability was named CVE-2015-8337. The attack needs to be approached locally. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Huawei P8 (Smartphone Operating System) (affected version unknown). This affects an unknown functionality of the component HiFi Driver. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. The summary by CVE is:
The HIFI driver in Huawei P8 phones with software GRA-TL00 before GRA-TL00C01B220SP01, GRA-CL00 before GRA-CL00C92B220, GRA-CL10 before GRA-CL10C92B220, GRA-UL00 before GRA-UL00C00B220, GRA-UL10 before GRA-UL10C00B220 and Mate7 phones with software MT7-UL00 before MT7-UL00C17B354, MT7-TL10 before MT7-TL10C00B354, MT7-TL00 before MT7-TL00C01B354, and MT7-CL00 before MT7-CL00C92B354 allows remote attackers to cause a denial of service (invalid memory access and reboot) via unspecified vectors related to "input null pointer as parameter."
The weakness was presented 01/12/2016 with Qihoo 360 (Website). The advisory is shared at huawei.com. This vulnerability is uniquely identified as CVE-2015-8337 since 11/24/2015. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 80357†). See VDB-80192 for similar entry. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.huawei.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
11/24/2015 🔍12/09/2015 🔍
01/12/2016 🔍
01/12/2016 🔍
01/13/2016 🔍
06/10/2018 🔍
Sources
Vendor: huawei.comAdvisory: huawei.com
Organization: Qihoo 360
Status: Not defined
CVE: CVE-2015-8337 (🔍)
GCVE (CVE): GCVE-0-2015-8337
GCVE (VulDB): GCVE-100-80193
SecurityFocus: 80357 - Huawei Smart Phones CVE-2015-8337 Multiple Local Denial of Service Vulnerabilities
See also: 🔍
Entry
Created: 01/13/2016 09:25Updated: 06/10/2018 09:04
Changes: 01/13/2016 09:25 (51), 06/10/2018 09:04 (11)
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.