# CVE-2018-3915: Memory corruption in SmartThings Hub STH-ETH-250

> A stack-based buffer overflow in the SmartThings Hub HTTP server allows remote attackers to execute arbitrary code via a long bucket value.

- **Severity:** High 7.5 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fwv9-q69x-v7q2

## What is CVE-2018-3915?

CVE-2018-3915 is a high-severity memory corruption vulnerability in Samsung SmartThings Hub STH-ETH-250, published on 21 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An exploitable stack-based buffer overflow vulnerability exists in the retrieval of database fields in the video-core HTTP server of the Samsung SmartThings Hub STH-ETH-250 - Firmware version 0.20.17. The strcpy call overflows the destination buffer, which has a size of 64 bytes. An attacker can send an arbitrarily long "bucket" value in order to exploit this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Samsung Sth-Eth-250 Firmware.

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

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

## Is CVE-2018-3915 being exploited?

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

## Other vulnerabilities in Samsung SmartThings Hub STH-ETH-250

- [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-3915 and fix it if it is affected.

What it is: CVE-2018-3915 is a high-severity memory corruption vulnerability in Samsung SmartThings Hub STH-ETH-250, published on 21 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3915 in the wild and no public exploit code.

Affected product: Samsung SmartThings Hub STH-ETH-250. 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-3915/ (Markdown: https://insights.sbomify.com/CVE-2018-3915/index.md)
```

## Sources

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

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