Product Huawei Smartphone

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

MHA-AL00AC00B1252
9.1.0.113(C00E110R1P21)1
9.1.0.125(C00E120R1P21)1
9.1.0.135(C00E130R1P21)1
9.1.0.153(C00E150R1P21)1

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Official Fix10
Temporary Fix0
Workaround0
Unavailable0
Not Defined140

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

High0
Functional0
Proof-of-Concept0
Unproven0
Not Defined150

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Not Defined0
Physical6
Local15
Adjacent113
Network16

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Not Defined0
High1
Low125
None24

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

Not Defined0
Required13
None137

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

≤10
≤20
≤31
≤460
≤514
≤662
≤79
≤84
≤90
≤100

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

≤10
≤20
≤30
≤42
≤52
≤622
≤73
≤87
≤91
≤109

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (14): 8.0.0.336a(C00), 9.0, 9.1, 9.1.0.113(C00E110R1P21), 9.1.0.125(C00E120R1P21), 9.1.0.135(C00E130R1P21), 9.1.0.153(C00E150R1P21), 9.1.0.155(C00E150R1P21), 9.1.0.162(C00E160R2P1), 10.0, ELLE-AL00B 9.1.0.109(C00E106R1P21), LON-L29DC721B186, MHA-AL00AC00B125, TAG-AL00C92B168

Link to Product Website: https://www.huawei.com/

Software Type: Smartphone Operating System

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
11/23/20213.53.5Huawei Smartphone Field Name information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37034
11/23/20213.53.5Huawei Smartphone injection$5k-$25k$5k-$25kNot DefinedNot Defined0.05CVE-2021-37033
11/23/20213.53.5Huawei Smartphone Digital Balance denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37032
11/23/20213.53.5Huawei Smartphone permission$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2021-37030
11/23/20213.53.5Huawei Smartphone Identity Verification denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37029
11/23/20215.55.5Huawei Smartphone Media File access control$5k-$25k$5k-$25kNot DefinedNot Defined0.05CVE-2021-37023
11/23/20213.53.5Huawei Smartphone denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37013
11/23/20213.53.5Huawei Smartphone information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37010
11/23/20213.53.5Huawei Smartphone config$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37009
11/23/20215.55.5Huawei Smartphone permission$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2021-37006
11/23/20214.34.3Huawei Smartphone App denial of service$5k-$25k$0-$5kNot DefinedNot Defined0.00CVE-2021-37035
11/23/20214.34.3Huawei Smartphone App denial of service$5k-$25k$0-$5kNot DefinedNot Defined0.00CVE-2021-37031
11/23/20215.75.7Huawei Smartphone Kernel denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37026
11/23/20215.75.7Huawei Smartphone Kernel denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37025
11/23/20215.75.7Huawei Smartphone Kernel denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37024
11/23/20218.08.0Huawei Smartphone heap-based overflow$5k-$25k$5k-$25kNot DefinedNot Defined0.05CVE-2021-37022
11/23/20215.75.7Huawei Smartphone Kernel denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37019
11/23/20215.75.7Huawei Smartphone Kernel denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37018
11/23/20215.75.7Huawei Smartphone Kernel denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37017
11/23/20213.53.5Huawei Smartphone out-of-bounds read$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37016
11/23/20215.75.7Huawei Smartphone Kernel out-of-bounds read$5k-$25k$0-$5kNot DefinedNot Defined0.00CVE-2021-37015
11/23/20215.75.7Huawei Smartphone Kernel denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37012
11/23/20215.75.7Huawei Smartphone Kernel denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37008
11/23/20215.75.7Huawei Smartphone Kernel out-of-bounds read$5k-$25k$0-$5kNot DefinedNot Defined0.00CVE-2021-37007
11/23/20215.75.7Huawei Smartphone Kernel denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-37005

125 more entries are not shown

more entries by Huawei

Do you want to use VulDB in your project?

Use the official API to access entries easily!