LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3914: 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 2000 bytes. An attacker can send an arbitrarily long "sessionToken" 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

CVE-2018-3914 is a memory corruption flaw in a Samsung SmartThings Hub firmware version. A specially oversized session token can overflow a fixed stack buffer in the hub's video-core HTTP server, potentially allowing serious compromise if an attacker can meet the access and privilege conditions.

Executive priority

Treat this as high priority where affected hubs are deployed on trusted or sensitive networks. The business risk is highest when IoT devices can bridge into corporate systems, but available evidence does not support emergency active-exploitation handling.

Technical view

The flaw is a stack-based buffer overflow in Samsung SmartThings Hub STH-ETH-250 firmware 0.20.17. During database field retrieval, a strcpy operation copies an attacker-controlled sessionToken into a 2000-byte destination buffer without adequate bounds enforcement. The CVSS vector indicates local access, high complexity, and high privileges.

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 models, later firmware versions, internet exposure requirements, or fleet prevalence.

Exploitation context

The source bundle states the flaw is exploitable, but CISA KEV status is false and no cited source states active exploitation. The CVSS vector suggests exploitation is constrained by local access, high complexity, and high privileges, despite high confidentiality, integrity, and availability impact.

Researcher notes

Key evidence is narrow: one affected model and firmware version, a specific strcpy overflow path, and CVSS 7.5. The bundle does not provide a patch version, exploitation-in-the-wild evidence, or broader affected-version ranges, so scope should remain conservative.

Mitigation direction

  • Inventory SmartThings Hub STH-ETH-250 devices and identify firmware version 0.20.17.
  • Check Samsung and Talos guidance for fixed firmware or supported mitigation details.
  • Restrict local network access to hub management and video-core HTTP interfaces.
  • Segment IoT hubs away from sensitive business systems and administrative workstations.
  • Retire or replace unsupported affected hubs if no vendor fix is available.

Validation and detection

  • Confirm whether any SmartThings Hub STH-ETH-250 runs firmware 0.20.17.
  • Review network controls limiting local access to the affected hub services.
  • Check asset records for SmartThings hubs connected to corporate or executive networks.
  • Look for vendor firmware update evidence before closing remediation tickets.
  • Do not validate using oversized tokens against production devices.
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-3914 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-3914Attack 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.