| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Huawei Mate S. Impacted is an unknown function of the component Graphics Driver. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2016-1495. The attack must be initiated from a local position. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Huawei Mate S (Smartphone Operating System) (affected version not known). It has been classified as critical. This affects some unknown functionality of the component Graphics Driver. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Integer overflow in the graphics drivers in Huawei Mate S smartphones with software CRR-TL00 before CRR-TL00C01B160SP01, CRR-UL00 before CRR-UL00C00B160, and CRR-CL00 before CRR-CL00C92B161 allows attackers to cause a denial of service (system crash) or gain privileges via a crafted application, which triggers a heap-based buffer overflow.
The weakness was shared 04/13/2016 with Qihoo 360 (Website). The advisory is shared at huawei.com. This vulnerability is uniquely identified as CVE-2016-1495 since 01/05/2016. 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 databases at SecurityFocus (BID 82509†) and Vulnerability Center (SBV-58241†). 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: 7.8VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: Memory corruptionCWE: CWE-119
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: 🔍
Timeline
01/05/2016 🔍02/03/2016 🔍
02/03/2016 🔍
04/13/2016 🔍
04/13/2016 🔍
04/14/2016 🔍
04/17/2016 🔍
07/24/2022 🔍
Sources
Vendor: huawei.comAdvisory: sa-20160203-01
Organization: Qihoo 360
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-1495 (🔍)
GCVE (CVE): GCVE-0-2016-1495
GCVE (VulDB): GCVE-100-82329
SecurityFocus: 82509 - Huawei Mate S CVE-2016-1495 Local Integer Overflow Vulnerability
Vulnerability Center: 58241 - Huawei Mate S Smartphones Remote Privileges Escalation via a Crafted Application, Critical
Entry
Created: 04/14/2016 09:59Updated: 07/24/2022 12:00
Changes: 04/14/2016 09:59 (54), 02/05/2019 12:35 (13), 07/24/2022 12:00 (3)
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.