Huawei Harmonyos Vulnerabilities

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.

Version

4.0.010
3.0.03
13.0.03
2.0.02
3.1.02

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.

Remediation

Official Fix53
Temporary Fix0
Workaround0
Unavailable0
Not Defined298

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.

Exploitability

High0
Functional0
Proof-of-Concept1
Unproven0
Not Defined350

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.

Access Vector

Not Defined0
Physical2
Local51
Adjacent273
Network25

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

Authentication

Not Defined0
High1
Low315
None35

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

User Interaction

Not Defined0
Required4
None347

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

C3BM Index

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.

Last Year

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.

CVSSv3 Base

≤10
≤21
≤33
≤463
≤531
≤6165
≤752
≤834
≤92
≤100

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.

CVSSv3 Temp

≤10
≤22
≤32
≤463
≤531
≤6167
≤750
≤834
≤92
≤100

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.

VulDB

≤10
≤21
≤36
≤4154
≤525
≤6147
≤78
≤89
≤91
≤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.

NVD

≤10
≤20
≤30
≤411
≤52
≤625
≤73
≤8127
≤91
≤1037

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

CNA

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

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤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.

Research

≤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.

Exploit 0-day

<1k1
<2k6
<5k76
<10k199
<25k69
<50k0
<100k0
≥100k0

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.

Exploit Today

<1k48
<2k21
<5k134
<10k127
<25k21
<50k0
<100k0
≥100k0

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.

Exploit Market Volume

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.

Last Year

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.

🔴 CTI Activities

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 (10): 2, 2.0, 2.0.1, 2.1, 3, 3.1, 4, 12, 12.0.1, 13

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

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
02/18/20245.55.5Huawei HarmonyOS/EMUI Control Panel Module Privilege Escalation$5k-$25k$5k-$25kNot DefinedNot Defined0.02CVE-2023-52363
02/18/20243.53.5Huawei HarmonyOS/EMUI Vibration Framework deserialization$5k-$25k$0-$5kNot DefinedNot Defined0.04CVE-2023-52357
02/18/20243.53.5Huawei HarmonyOS/EMUI NMS Module information disclosure$5k-$25k$0-$5kNot DefinedNot Defined0.04CVE-2023-52097
02/18/20243.53.5Huawei HarmonyOS/EMUI Lock Screen Module permission$5k-$25k$0-$5kNot DefinedNot Defined0.03CVE-2023-52362
02/18/20244.34.3Huawei HarmonyOS VerifiedBoot Module improper authentication$5k-$25k$5k-$25kNot DefinedNot Defined0.02CVE-2023-52361
02/18/20243.53.5Huawei HarmonyOS/EMUI GPU Module information disclosure$5k-$25k$0-$5kNot DefinedNot Defined0.02CVE-2023-52387
02/18/20243.53.5Huawei HarmonyOS/EMUI Baseband unknown vulnerability$5k-$25k$5k-$25kNot DefinedNot Defined0.03CVE-2023-52360
02/18/20243.53.5Huawei HarmonyOS/EMUI access control$5k-$25k$0-$5kNot DefinedNot Defined0.02CVE-2023-52374
02/18/20245.55.5Huawei HarmonyOS/EMUI Cellular Data Module buffer overflow$5k-$25k$5k-$25kNot DefinedNot Defined0.02CVE-2023-52377
02/18/20243.53.5Huawei HarmonyOS/EMUI Gallery Module information management$5k-$25k$0-$5kNot DefinedNot Defined0.02CVE-2023-52376
02/18/20243.53.5Huawei HarmonyOS/EMUI WindowManagerServices Module access control$5k-$25k$0-$5kNot DefinedNot Defined0.02CVE-2023-52375
02/18/20245.55.5Huawei HarmonyOS/EMUI Email Module code injection$5k-$25k$5k-$25kNot DefinedNot Defined0.04CVE-2023-52381
02/18/20243.53.5Huawei HarmonyOS/EMUI Email Module access control$5k-$25k$5k-$25kNot DefinedNot Defined0.04CVE-2023-52380
02/18/20243.53.5Huawei HarmonyOS/EMUI calendarProvider module access control$5k-$25k$0-$5kNot DefinedNot Defined0.04CVE-2023-52379
02/18/20245.55.5Huawei HarmonyOS/EMUI WindowManagerServices Module Privilege Escalation$5k-$25k$5k-$25kNot DefinedNot Defined0.04CVE-2023-52378
02/18/20244.34.3Huawei HarmonyOS/EMUI Wi-Fi Module missing authentication$5k-$25k$5k-$25kNot DefinedNot Defined0.04CVE-2022-48621
02/18/20243.53.5Huawei HarmonyOS/EMUI Audio Module denial of service$5k-$25k$0-$5kNot DefinedNot Defined0.02CVE-2023-52358
02/18/20243.53.5Huawei HarmonyOS/EMUI Smart Activity Recognition Module out-of-bounds$5k-$25k$0-$5kNot DefinedNot Defined0.02CVE-2023-52365
02/18/20245.55.5Huawei HarmonyOS/EMUI Media Library Module access control$5k-$25k$5k-$25kNot DefinedNot Defined0.02CVE-2023-52367
02/18/20243.53.5Huawei HarmonyOS/EMUI Smart Activity Recognition Module out-of-bounds$5k-$25k$0-$5kNot DefinedNot Defined0.03CVE-2023-52366
02/18/20245.55.5Huawei HarmonyOS/EMUI Account Module input validation$5k-$25k$5k-$25kNot DefinedNot Defined0.02CVE-2023-52368
02/18/20243.53.5Huawei HarmonyOS/EMUI Motor Module null pointer dereference$5k-$25k$0-$5kNot DefinedNot Defined0.03CVE-2023-52371
02/18/20246.36.3Huawei HarmonyOS/EMUI Network Acceleration Module stack-based overflow$5k-$25k$5k-$25kNot DefinedNot Defined0.02CVE-2023-52370
02/18/20245.55.5Huawei HarmonyOS/EMUI NFC Module stack-based overflow$5k-$25k$5k-$25kNot DefinedNot Defined0.02CVE-2023-52369
02/18/20244.34.3Huawei HarmonyOS/EMUI Content Sharing Pop-Up Module access control$5k-$25k$5k-$25kNot DefinedNot Defined0.05CVE-2023-52373

326 more entries are not shown

more entries by Huawei

Might our Artificial Intelligence support you?

Check our Alexa App!