# CVE-2018-3918: Business logic in Samsung

> An attacker can send unauthenticated HTTP requests to delete arbitrary cameras due to improper handling of camera IDs in the sync operation.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **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:** 17 Sep 2024
- **Also known as:** GHSA-7fjm-q9xv-4f29

## What is CVE-2018-3918?

CVE-2018-3918 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 vulnerability exists in the remote servers of Samsung SmartThings Hub STH-ETH-250 - Firmware version 0.20.17. The hubCore process listens on port 39500 and relays any unauthenticated messages to SmartThings' remote servers, which incorrectly handle camera IDs for the 'sync' operation, leading to arbitrary deletion of cameras. An attacker can send an HTTP request to trigger this vulnerability.

Weakness: CWE-707 (Improper Neutralization)

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

It affects 1 product.


Products: Samsung Sth-Eth-250 Firmware.

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

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

## Is CVE-2018-3918 being exploited?

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

What it is: CVE-2018-3918 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-3918 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-3918/ (Markdown: https://insights.sbomify.com/CVE-2018-3918/index.md)
```

## Sources

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

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