iSmartAlarm App up to 2.0.8 on Android Configuration File iSmartAlarmData.xml Credentials credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in iSmartAlarm App up to 2.0.8 on Android. This vulnerability affects unknown code of the file iSmartAlarmData.xml of the component Configuration File. The manipulation results in credentials management (Credentials). This vulnerability is known as CVE-2018-16222. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability, which was classified as problematic, was found in iSmartAlarm App up to 2.0.8 on Android (Android App Software). Affected is an unknown code block of the file iSmartAlarmData.xml of the component Configuration File. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Cleartext Storage of credentials in the iSmartAlarmData.xml configuration file in the iSmartAlarm application through 2.0.8 for Android allows an attacker to retrieve the username and password.
The bug was discovered 10/31/2018. The weakness was published 11/20/2018 as not defined mailinglist post (Full-Disclosure). The advisory is shared for download at seclists.org. This vulnerability is traded as CVE-2018-16222 since 08/30/2018. The attack needs to be approached locally. The requirement for exploitation is a authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1552.
The vulnerability was handled as a non-public zero-day exploit for at least 20 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:iSmartAlarmData.xml it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-127021 and VDB-127022. Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.8
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Name: CredentialsClass: Credentials management / Credentials
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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
08/30/2018 🔍10/31/2018 🔍
11/20/2018 🔍
11/20/2018 🔍
11/21/2018 🔍
06/11/2023 🔍
Sources
Advisory: 150165Status: Not defined
CVE: CVE-2018-16222 (🔍)
GCVE (CVE): GCVE-0-2018-16222
GCVE (VulDB): GCVE-100-127020
scip Labs: https://www.scip.ch/en/?labs.20130704
See also: 🔍
Entry
Created: 11/21/2018 12:12Updated: 06/11/2023 08:20
Changes: 11/21/2018 12:12 (62), 04/14/2020 09:49 (1), 06/11/2023 08:20 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.