# CVE-2018-3909: Other in Samsung

> An attacker can exploit HTTP request pipelining in the SmartThings Hub video-core server to overwrite parsed data, potentially leading to code execution.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 24 Aug 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-59hg-jxh2-2qg8

## What is CVE-2018-3909?

CVE-2018-3909 is a critical vulnerability in Talos Samsung, published on 24 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 REST parser of video-core's HTTP server of the Samsung SmartThings Hub STH-ETH-250 - Firmware version 0.20.17. The video-core process incorrectly handles pipelined HTTP requests, which allows successive requests to overwrite the previously parsed HTTP method, 'onmessagecomplete' callback. An attacker can send an HTTP request to trigger this vulnerability.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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

It affects 1 product.


Products: Samsung Sth-Eth-250 Firmware.

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

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

## Is CVE-2018-3909 being exploited?

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

## Other vulnerabilities in Talos 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-3909 and fix it if it is affected.

What it is: CVE-2018-3909 is a critical vulnerability in Talos Samsung, published on 24 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-3909 in the wild and no public exploit code.

Affected product: Talos 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-3909/ (Markdown: https://insights.sbomify.com/CVE-2018-3909/index.md)
```

## Sources

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

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