| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenHarmony up to 4.0.0. It has been classified as critical. Affected is an unknown function. The manipulation leads to permissions. This vulnerability is uniquely identified as CVE-2024-21816. Local access is required to approach this attack. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability was found in OpenHarmony up to 4.0.0. It has been rated as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a permissions vulnerability. Using CWE to declare the problem leads to CWE-281. The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended. Impacted is confidentiality. The summary by CVE is:
in OpenHarmony v4.0.0 and prior versions allow a local attacker cause information leak through improper preservation of permissions.
The weakness was disclosed 03/04/2024. The advisory is shared at gitee.com. The identification of this vulnerability is CVE-2024-21816 since 01/06/2024. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
Upgrading to version 4.0.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 4.0
CNA Vector (OpenHarmony): 🔍
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: 🔍
Exploiting
Class: PermissionsCWE: CWE-281 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: 🔍
0-Day Time: 🔍
Upgrade: OpenHarmony 4.0.1
Timeline
01/06/2024 🔍03/04/2024 🔍
03/04/2024 🔍
12/16/2024 🔍
Sources
Advisory: gitee.comStatus: Confirmed
CVE: CVE-2024-21816 (🔍)
GCVE (CVE): GCVE-0-2024-21816
GCVE (VulDB): GCVE-100-255617
Entry
Created: 03/04/2024 08:05Updated: 12/16/2024 21:30
Changes: 03/04/2024 08:05 (47), 04/04/2024 11:09 (15), 12/16/2024 21:30 (14)
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.