Belwith Products Hickory Smart 01.01.43 on Android Debug Log Event log file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Belwith Products Hickory Smart 01.01.43 on Android. Impacted is an unknown function of the component Debug Log Event Handler. Such manipulation leads to log file. This vulnerability is traded as CVE-2019-5634. An attack has to be approached locally. There is no exploit available.
Details
A vulnerability was found in Belwith Products Hickory Smart 01.01.43 on Android (Android App Software) and classified as problematic. Affected by this issue is an unknown code block of the component Debug Log Event Handler. The manipulation with an unknown input leads to a log file vulnerability. Using CWE to declare the problem leads to CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. Impacted is confidentiality. CVE summarizes:
An inclusion of sensitive information in log files vulnerability is present in Hickory Smart for Android mobile devices from Belwith Products, LLC. Communications to the internet API services and direct connections to the lock via Bluetooth Low Energy (BLE) from the mobile application are logged in a debug log on the Android device at HickorySmartLog/Logs/SRDeviceLog.txt. This information was found stored in the Android device's default USB or SDcard storage paths and is accessible without rooting the device. This issue affects Hickory Smart for Android, version 01.01.43 and prior versions.
The weakness was shared 08/22/2019. This vulnerability is handled as CVE-2019-5634 since 01/07/2019. The attack needs to be approached locally. The requirement for exploitation is a simple authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-140683 and VDB-140682 are related to this item. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
CNA Base Score: 6.5
CNA Vector (Rapid7, Inc.): 🔍
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
Class: Log fileCWE: CWE-532 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
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/07/2019 🔍08/22/2019 🔍
08/23/2019 🔍
12/01/2023 🔍
Sources
Advisory: blog.rapid7.comStatus: Not defined
CVE: CVE-2019-5634 (🔍)
GCVE (CVE): GCVE-0-2019-5634
GCVE (VulDB): GCVE-100-140684
scip Labs: https://www.scip.ch/en/?labs.20130704
See also: 🔍
Entry
Created: 08/23/2019 09:18Updated: 12/01/2023 11:22
Changes: 08/23/2019 09:18 (37), 08/04/2020 07:39 (18), 12/01/2023 11:14 (3), 12/01/2023 11:22 (12)
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.