| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in OpenHarmony up to 3.2.4. This vulnerability affects unknown code. Performing a manipulation results in sensitive information. This vulnerability is identified as CVE-2024-21826. The attack is only possible with local access. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, was found in OpenHarmony up to 3.2.4. This affects some unknown functionality. The manipulation with an unknown input leads to a sensitive information vulnerability. CWE is classifying the issue as CWE-922. The product stores sensitive information without properly limiting read or write access by unauthorized actors. This is going to have an impact on confidentiality. The summary by CVE is:
in OpenHarmony v3.2.4 and prior versions allow a local attacker cause sensitive information leak through insecure storage.
The weakness was released 03/04/2024. The advisory is shared at gitee.com. This vulnerability is uniquely identified as CVE-2024-21826 since 01/06/2024. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 4.3
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: Sensitive informationCWE: CWE-922 / CWE-200 / CWE-284
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/06/2024 🔍03/04/2024 🔍
03/04/2024 🔍
12/16/2024 🔍
Sources
Advisory: gitee.comStatus: Confirmed
CVE: CVE-2024-21826 (🔍)
GCVE (CVE): GCVE-0-2024-21826
GCVE (VulDB): GCVE-100-255621
Entry
Created: 03/04/2024 08:05Updated: 12/16/2024 21:30
Changes: 03/04/2024 08:05 (44), 04/04/2024 11:41 (15), 12/16/2024 21:30 (14)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.