CVE-2019-5632
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn insecure storage of sensitive information vulnerability is present in Hickory Smart for Android mobile devices from Belwith Products, LLC. The application's database was found to contain information that could be used to control the lock devices remotely. This issue affects Hickory Smart for Android, version 01.01.43 and prior versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Hickory Smart Android application stores sensitive lock control credentials or tokens in an unencrypted local database. Any attacker with physical access to the device or malware capable of reading the app's local storage can extract these credentials and use them to remotely control the associated smart locks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 01.01.43CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Hickory Smart app is installedOpen Android Settings > Apps > Look for 'Hickory Smart' or 'Belwith Keeler Hickory Smart' in the installed apps list. Note the version number displayed.Affected if The app is installed and its version is 01.01.43 or lower
-
Verify the installed version against affected rangeCompare the installed version number to the affected range. The app version is typically shown on the Google Play Store listing or in the app's 'About' section under Settings.Affected if Version is 01.01.43 or lower (any version up to and including 01.01.43)
-
Examine app data directory for unencrypted databasesIf root access is available, navigate to /data/data/com.hickorysmart or use ADB to pull the app's internal storage. Look for SQLite database files (.db) in the databases folder.Affected if SQLite database files exist in the app's private directory and contain plaintext credentials or tokens
-
Inspect shared preferences for plaintext sensitive dataIf root access is available, examine the shared_prefs folder within the app's data directory. Look for XML files that may contain lock credentials, authentication tokens, or other sensitive data in plaintext.Affected if Shared preferences files contain plaintext sensitive data such as passwords, tokens, or lock control credentials
A user is affected if the Hickory Smart Android app version 01.01.43 or lower is installed and contains plaintext lock credentials or tokens in local storage.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataMigrate sensitive lock control data to encrypted storage using Android Keystore-backed EncryptedSharedPreferences or similar secure storage mechanisms; verify no sensitive data remains in plaintext in databases or shared preferences.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5632 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5632 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data