LiveActive security incident?Get immediate response
CVE Record

CVE-2019-5634: Hickory Smart Lock Insecure Logging on Android

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

The Hickory Smart Android app logged sensitive smart-lock communications to a file on ordinary device storage. A person or app with local access to the Android device could read this without rooting the phone, creating a confidentiality risk around lock/API and BLE communication data.

Executive priority

Treat as a targeted confidentiality issue for organizations still using these locks. It is not internet-remote by itself, but exposed lock communication data on a phone can become operationally sensitive if devices are shared, lost, or accessed by untrusted apps.

Technical view

CVE-2019-5634 is CWE-532 sensitive information in log files affecting Hickory Smart for Android version 01.01.43 and prior. The app stored internet API and BLE lock communication details in HickorySmartLog/Logs/SRDeviceLog.txt on default USB or SDcard storage paths accessible without root.

Likely exposure

Exposure is likely limited to Android devices running Hickory Smart version 01.01.43 or earlier, especially where device storage is accessible to other local apps, USB access, or people handling the device.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not state active exploitation. The attack model is local access with low complexity and low privileges, focused on confidentiality rather than integrity or availability.

Researcher notes

Evidence supports insecure local logging, not code execution or remote compromise. The source bundle does not identify a specific patch version or vendor mitigation, so remediation should be validated against current vendor guidance rather than assumed.

Mitigation direction

  • Inventory Android devices using Hickory Smart.
  • Check installed app versions for 01.01.43 or earlier.
  • Check Belwith or Google Play guidance for updated software.
  • Remove affected app logs from device storage where authorized.
  • Restrict device access until vendor guidance is confirmed.

Validation and detection

  • Confirm whether Hickory Smart is installed on Android devices.
  • Verify app version against 01.01.43 and prior.
  • Check authorized devices for HickorySmartLog/Logs/SRDeviceLog.txt.
  • Review whether logs contain sensitive API or BLE communications.
  • Confirm affected logs are removed after remediation.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-532: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-5634 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.0MediumCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N24Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.5Medium
CVSS 3.0 vector shape for CVE-2019-5634Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Belwith Products, LLCHickory SmartunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-532 · source CWE mapping

Insertion of Sensitive Information into Log File

Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.