Samsung SmartThings Hub STH-ETH-250 0.20.17 Video Core memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Samsung SmartThings Hub STH-ETH-250 0.20.17. The impacted element is an unknown function of the component Video Core. The manipulation leads to memory corruption. This vulnerability is referenced as CVE-2018-3878. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability, which was classified as critical, has been found in Samsung SmartThings Hub STH-ETH-250 0.20.17 (Router Operating System). This issue affects some unknown processing of the component Video Core. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Multiple exploitable buffer overflow vulnerabilities exist 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 extracts fields from a user-controlled JSON payload, leading to a buffer overflow on the stack. A strncpy overflows the destination buffer, which has a size of 16 bytes. An attacker can send an arbitrarily long "region" value in order to exploit this vulnerability.
The bug was discovered 07/26/2018. The weakness was published 08/23/2018 (Website). The advisory is shared at talosintelligence.com. The identification of this vulnerability is CVE-2018-3878 since 01/01/2018. The exploitation is known to be easy. The attack may be initiated remotely. Required for exploitation is a simple authentication. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 28 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-123189, VDB-123188, VDB-123187 and VDB-123186. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.1VulDB Meta Temp Score: 9.1
VulDB Base Score: 7.4
VulDB Temp Score: 7.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.9
NVD Vector: 🔍
CNA Base Score: 9.9
CNA Vector (Talos): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/01/2018 🔍07/26/2018 🔍
08/23/2018 🔍
08/23/2018 🔍
08/24/2018 🔍
05/04/2023 🔍
Sources
Vendor: samsung.comAdvisory: talosintelligence.com
Status: Not defined
CVE: CVE-2018-3878 (🔍)
GCVE (CVE): GCVE-0-2018-3878
GCVE (VulDB): GCVE-100-123185
See also: 🔍
Entry
Created: 08/24/2018 07:03Updated: 05/04/2023 11:05
Changes: 08/24/2018 07:03 (58), 03/17/2020 19:18 (1), 05/04/2023 11:05 (14)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.