Huawei HarmonyOS/EMUI config

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Huawei HarmonyOS and EMUI. This issue affects some unknown processing. The manipulation leads to config. This vulnerability is traded as CVE-2024-54099. An attack has to be approached locally. There is no exploit available.

Detailsinfo

A vulnerability was found in Huawei HarmonyOS and EMUI (affected version unknown) and classified as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a config vulnerability. Using CWE to declare the problem leads to CWE-16. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

File replacement vulnerability on some devices Impact: Successful exploitation of this vulnerability will affect integrity and confidentiality.

The advisory is shared at consumer.huawei.com. The identification of this vulnerability is CVE-2024-54099 since 11/29/2024. The exploitation is known to be easy. An attack has to be approached locally. Additional levels of successful authentication are needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/18/2025). MITRE ATT&CK project uses the attack technique T1592.004 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-52275). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.0
VulDB Meta Temp Score: 6.0

VulDB Base Score: 4.2
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.1
NVD Vector: 🔍

CNA Base Score: 6.7
CNA Vector (huawei): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Config
CWE: CWE-16
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/29/2024 🔍
12/12/2024 +13 days 🔍
12/12/2024 +0 days 🔍
09/18/2025 +280 days 🔍

Sourcesinfo

Vendor: huawei.com

Advisory: consumer.huawei.com
Status: Confirmed

CVE: CVE-2024-54099 (🔍)
GCVE (CVE): GCVE-0-2024-54099
GCVE (VulDB): GCVE-100-288149
EUVD: 🔍

Entryinfo

Created: 12/12/2024 12:49
Updated: 09/18/2025 19:47
Changes: 12/12/2024 12:49 (60), 01/11/2025 02:01 (12), 09/18/2025 19:47 (1)
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 want to use VulDB in your project?

Use the official API to access entries easily!