LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3915: An exploitable stack-based buffer overflow vulnerability exists in the retrieval of database fields in the...

An exploitable stack-based buffer overflow vulnerability exists in the retrieval of database fields in the video-core HTTP server of the Samsung SmartThings Hub STH-ETH-250 - Firmware version 0.20.17. The strcpy call overflows the destination buffer, which has a size of 64 bytes. An attacker can send an arbitrarily long "bucket" value in order to exploit this vulnerability.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects Samsung SmartThings Hub STH-ETH-250 firmware 0.20.17. A vulnerable HTTP server component can overflow memory when handling an overly long database field value. Successful exploitation could compromise confidentiality, integrity, and availability, but the CVSS vector indicates local access, high privileges, and high complexity are required.

Executive priority

Treat this as a targeted local-risk issue, not an internet-scale emergency. Prioritize it where SmartThings hubs bridge sensitive networks, support physical operations, or remain on old firmware without vendor support.

Technical view

CVE-2018-3915 is a stack-based buffer overflow in the video-core HTTP server during database field retrieval. The source description identifies an unsafe strcpy into a 64-byte destination buffer using the attacker-controlled bucket value. The published CVSS v3.0 score is 7.5 with AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H.

Likely exposure

Exposure appears limited to Samsung SmartThings Hub STH-ETH-250 devices running firmware 0.20.17. The provided sources do not identify other affected versions or products. The local, high-privilege CVSS prerequisites reduce broad internet exposure but matter in compromised local networks or poorly controlled administrative environments.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The vulnerability is described as exploitable, but the reported attack prerequisites are restrictive: local access, high privileges, no user interaction, and high attack complexity.

Researcher notes

Key evidence is narrow: one affected model and firmware version, one Talos report reference, and the CVE description. Do not generalize to all SmartThings hubs without vendor evidence. Validation should focus on asset identity, firmware version, reachable local services, and compensating controls.

Mitigation direction

  • Inventory Samsung SmartThings Hub STH-ETH-250 devices and firmware versions.
  • Check Samsung or SmartThings guidance for fixed firmware or replacement direction.
  • Prioritize updating or retiring devices confirmed on firmware 0.20.17.
  • Restrict management and local network access to trusted administrators only.
  • Segment smart hub networks away from sensitive business systems.

Validation and detection

  • Confirm whether any STH-ETH-250 hubs run firmware 0.20.17.
  • Verify update status against current Samsung or SmartThings vendor guidance.
  • Review network paths that can reach the hub HTTP service.
  • Check administrative access controls for unnecessary local privileged users.
  • Look for unexplained hub crashes or resets in operational logs.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-3915 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.0HighCVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H0.86Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.5High
CVSS 3.0 vector shape for CVE-2018-3915Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SamsungSmartThings Hub STH-ETH-250Firmware version 0.20.17Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.