Huawei P30 up to 9.1.0 Parameter data authenticity

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.
4.9$0-$5k0.00

Summaryinfo

A vulnerability was found in Huawei P30 up to 9.1.0. It has been classified as critical. The affected element is an unknown function. Performing a manipulation as part of Parameter results in data authenticity. This vulnerability is reported as CVE-2019-5229. The attack may be carried out on the physical device. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Huawei P30 up to 9.1.0 (Smartphone Operating System). It has been classified as problematic. This affects an unknown code block. The manipulation as part of a Parameter leads to a data authenticity vulnerability. CWE is classifying the issue as CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

P30 smartphones with versions earlier than ELLE-AL00B 9.1.0.193(C00E190R2P1) have an insufficient verification vulnerability. The system does not verify certain parameters sufficiently, an attacker should connect to the phone and gain high privilege to launch the attack, successful exploit could cause malicious code execution.

The weakness was disclosed 11/12/2019. This vulnerability is uniquely identified as CVE-2019-5229 since 01/04/2019. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version ELLE-AL00B 9.1.0.193(C00E190R2P1) eliminates this vulnerability.

The entry VDB-145439 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.9
VulDB Meta Temp Score: 4.9

VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.2
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Data authenticity
CWE: CWE-345
CAPEC: 🔍
ATT&CK: 🔍

Physical: Yes
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: P30 ELLE-AL00B 9.1.0.193(C00E190R2P1)

Timelineinfo

01/04/2019 🔍
11/12/2019 +312 days 🔍
11/13/2019 +1 days 🔍
02/13/2024 +1553 days 🔍

Sourcesinfo

Vendor: huawei.com

Advisory: sa-20190925-02
Status: Not defined

CVE: CVE-2019-5229 (🔍)
GCVE (CVE): GCVE-0-2019-5229
GCVE (VulDB): GCVE-100-145437
See also: 🔍

Entryinfo

Created: 11/13/2019 12:30
Updated: 02/13/2024 10:01
Changes: 11/13/2019 12:30 (38), 11/13/2019 12:35 (18), 02/13/2024 10:01 (4)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!