Samsung SmartThings Hub STH-ETH-250 0.20.17 Video-Core Process HTTP Request memory corruption

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.9 | $0-$5k | 0.00 |
A vulnerability classified as critical was found in Samsung SmartThings Hub STH-ETH-250 0.20.17 (Router Operating System). Affected by this vulnerability is an unknown function of the component Video-Core Process. The manipulation as part of a HTTP Request leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
On Samsung SmartThings Hub STH-ETH-250 devices with firmware version 0.20.17, the video-core process insecurely extracts the fields from the "shard" table of its SQLite database, leading to a buffer overflow on the stack. An attacker can send an HTTP request to trigger this vulnerability. The strcpy call 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 presented 08/23/2018 (Website). The advisory is shared at talosintelligence.com. This vulnerability is known as CVE-2018-3917 since 01/01/2018. The exploitation appears to be easy. The attack can be launched remotely. The successful exploitation requires a single 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.
See VDB-123192 for similar entry. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.9VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.9
NVD Vector: 🔍
CNA Base Score: 7.5
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: 🔍
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-3917 (🔍)
GCVE (CVE): GCVE-0-2018-3917
GCVE (VulDB): GCVE-100-123193
See also: 🔍
Entry
Created: 08/24/2018 08:12 AMUpdated: 05/04/2023 12:00 PM
Changes: 08/24/2018 08:12 AM (60), 03/17/2020 08:10 PM (1), 05/04/2023 12:00 PM (14)
Complete: 🔍
Cache ID: 18:51D:40
No comments yet. Languages: en.
Please log in to comment.