# CVE-2018-3879: SQL injection in SmartThings Hub STH-ETH-250

> Attacker can inject SQL via JSON payload in HTTP requests to manipulate the video-core database on Samsung SmartThings Hub devices.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wrgr-53r5-77j3

## What is CVE-2018-3879?

CVE-2018-3879 is a high-severity SQL injection vulnerability in Samsung SmartThings Hub STH-ETH-250, published on 23 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An exploitable JSON injection vulnerability exists in the credentials handler of video-core's HTTP server of Samsung SmartThings Hub STH-ETH-250 devices with firmware version 0.20.17. The video-core process incorrectly parses the user-controlled JSON payload, leading to a JSON injection which in turn leads to a SQL injection in the video-core database. An attacker can send a series of HTTP requests to trigger this vulnerability.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Samsung Sth-Eth-250 Firmware.

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

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

## Is CVE-2018-3879 being exploited?

There is no known exploitation of CVE-2018-3879 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-3879 and fix it if it is affected.

What it is: CVE-2018-3879 is a high-severity SQL injection vulnerability in Samsung SmartThings Hub STH-ETH-250, published on 23 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3879 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-3879/ (Markdown: https://insights.sbomify.com/CVE-2018-3879/index.md)
```

## Sources

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

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