CVE Intelligence
Skip to main content
MEDIUM

CVE-2019-5635

CVE-2019-5635 — Hickory Smart Lock Cleartext Password

A cleartext transmission of sensitive information vulnerability is present in Hickory Smart Ethernet Bridge from Belwith Products, LLC. Captured data reveals that the Hickory Smart Ethernet Bridge device communicates over the network to an MQTT broker without using encryption. This exposed the default username and password used to authenticate to the MQTT broker. This issue affects Hickory Smart Ethernet Bridge, model number H077646. The firmware does not appear to contain versioning information.

Published Updated Sources: cvelistV5, rapid7

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

belwith products

hickory_smart_ethernet_bridge

CVSS base

6.5

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

belwith products

Products (1)

hickory smart ethernet bridge

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
6.5CVSS 3.0MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-319

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1056.004Input Capture: Credential API Hooking
  • T1040Network Sniffing

References

2 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.