CVE-2018-3927

MEDIUMCVSS 6.8/10EPSS 1.14%

Last modified

CVE-2018-3927 is a medium-severity vulnerability rated 6.8/10 on the CVSS scale. An exploitable information disclosure vulnerability exists in the crash handler of the hubCore binary of the Samsung SmartThings Hub STH-ETH-250 - Firmware version 0.20.17. When hubCore crashes, Google Breakpad is used to record minidumps, which are sent over an insecure HTTPS connection to the backtrace.io service, leading to the exposure of sensitive data. EPSS estimates a 1.14% chance of exploitation in the next 30 days.

Description

An exploitable information disclosure vulnerability exists in the crash handler of the hubCore binary of the Samsung SmartThings Hub STH-ETH-250 - Firmware version 0.20.17. When hubCore crashes, Google Breakpad is used to record minidumps, which are sent over an insecure HTTPS connection to the backtrace.io service, leading to the exposure of sensitive data. An attacker can impersonate the remote backtrace.io server in order to trigger this vulnerability.

Metrics

CVSS 3.0
6.8/10

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

EPSS Probability
1.14%

62.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
SamsungSth-Eth-250 Firmware0.20.17

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2018-3927?
An exploitable information disclosure vulnerability exists in the crash handler of the hubCore binary of the Samsung SmartThings Hub STH-ETH-250 - Firmware version 0.20.17. When hubCore crashes, Google Breakpad is used to record minidumps, which are sent over an insecure HTTPS connection to the backtrace.io service, leading to the exposure of sensitive data. An attacker can impersonate the remote backtrace.io server in order to trigger this vulnerability.
How severe is CVE-2018-3927?
CVE-2018-3927 has a CVSS score of 6.8/10 (MEDIUM severity). The EPSS model estimates a 1.14% probability of exploitation in the next 30 days.
How do I fix CVE-2018-3927?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2018

Are you affected by CVE-2018-3927?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST