| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Xiaomi App Market up to 4.57.4. The impacted element is an unknown function of the component Configuration Handler. Performing a manipulation results in an unknown weakness. This vulnerability is reported as CVE-2023-26323. The attacker must have access to the local network to execute the attack. No exploit exists.
Details
A vulnerability, which was classified as problematic, was found in Xiaomi App Market up to 4.57.4. This affects an unknown functionality of the component Configuration Handler. This is going to have an impact on integrity, and availability. The summary by CVE is:
A code execution vulnerability exists in the Xiaomi App market product. The vulnerability is caused by unsafe configuration and can be exploited by attackers to execute arbitrary code.
The advisory is shared at trust.mi.com. This vulnerability is uniquely identified as CVE-2023-26323 since 02/22/2023. The exploitability is told to be easy. The attack can only be done within the local network. 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/13/2024).
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
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 4.6
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 7.6
CNA Vector (Xiaomi): 🔍
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: UnknownCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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
02/22/2023 🔍08/28/2024 🔍
08/28/2024 🔍
09/13/2024 🔍
Sources
Advisory: trust.mi.comStatus: Confirmed
CVE: CVE-2023-26323 (🔍)
GCVE (CVE): GCVE-0-2023-26323
GCVE (VulDB): GCVE-100-275997
Entry
Created: 08/28/2024 10:49Updated: 09/13/2024 09:15
Changes: 08/28/2024 10:49 (60), 08/29/2024 10:35 (1), 09/13/2024 09:15 (11)
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.