# CVE-2018-3927: Information disclosure in Samsung

> An attacker can intercept crash reports sent by the SmartThings Hub to expose sensitive data due to insecure HTTPS validation.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-53x2-3mx9-q64r

## What is CVE-2018-3927?

CVE-2018-3927 is a medium-severity vulnerability in Samsung, published on 27 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2018-3927?

It affects 1 product.


Products: Samsung Sth-Eth-250 Firmware.

## How do I fix CVE-2018-3927?

No fix has been published for CVE-2018-3927 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-3927 being exploited?

There is no known exploitation of CVE-2018-3927 in the wild and no public exploit code.

## Other vulnerabilities in Samsung

- [CVE-2018-3873](https://insights.sbomify.com/CVE-2018-3873/): Memory corruption in SmartThings Hub STH-ETH-250 (critical 9.9)
- [CVE-2018-3874](https://insights.sbomify.com/CVE-2018-3874/): Memory corruption in SmartThings Hub STH-ETH-250 (critical 9.9)
- [CVE-2018-3876](https://insights.sbomify.com/CVE-2018-3876/): Memory corruption in SmartThings Hub STH-ETH-250 (critical 9.9)
- [CVE-2018-3877](https://insights.sbomify.com/CVE-2018-3877/): Memory corruption in SmartThings Hub STH-ETH-250 (critical 9.9)
- [CVE-2018-3894](https://insights.sbomify.com/CVE-2018-3894/): Memory corruption in SmartThings Hub STH-ETH-250 (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3927 and fix it if it is affected.

What it is: CVE-2018-3927 is a medium-severity vulnerability in Samsung, published on 27 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3927 in the wild and no public exploit code.

Affected product: Samsung. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-3927/ (Markdown: https://insights.sbomify.com/CVE-2018-3927/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-3927
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-3927
- OSV: https://osv.dev/vulnerability/CVE-2018-3927

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-3927/
Summaries are generated and may contain mistakes; the official description above is the record.