LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16318: Multiple exploitable buffer overflow vulnerabilities exist in the PubNub message handler for the "cc" chann...

Multiple exploitable buffer overflow vulnerabilities exist in the PubNub message handler for the "cc" channel of Insteon Hub running firmware version 1012. Specially crafted commands sent through the PubNub service can cause a stack-based buffer overflow overwriting arbitrary data. An attacker should send an authenticated HTTP request to trigger this vulnerability. In cmd s_sonos, at 0x9d01d16c, the value for the `g_group_off` key is copied using `strcpy` to the buffer at `$sp+0x2b0`.This buffer is 32 bytes large, sending anything longer will cause a buffer overflow.

HighCVSS 8.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-16318 is a high-severity memory corruption issue in the Insteon Hub PubNub message handler. A logged-in attacker could send a specially crafted command that overflows a small stack buffer, potentially compromising confidentiality, integrity, and availability of the device.

Executive priority

Treat this as a high-priority legacy device risk where Insteon Hubs remain in use. The main business concern is that compromise of a connected automation hub may affect physical environment controls and broader network trust.

Technical view

The reported flaw is a CWE-121 stack-based buffer overflow in Insteon Hub firmware 1012. In cmd s_sonos, the g_group_off value is copied with strcpy into a 32-byte stack buffer, allowing oversized authenticated input through the PubNub cc channel to overwrite stack data.

Likely exposure

Exposure is most relevant where Insteon Hubs, especially firmware 1012, are deployed and reachable through their expected PubNub-connected control path. The source bundle does not specify all affected versions or deployment prerequisites beyond authenticated HTTP interaction.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. Exploitation requires authenticated access and crafted input, but successful exploitation could have high device impact.

Researcher notes

Evidence is strongest for firmware 1012 and the specific strcpy stack overflow path. The provided sources do not name a patch, broad affected-version range, or exploitation in the wild, so remediation should be tied to vendor-confirmed guidance.

Mitigation direction

  • Inventory Insteon Hub deployments and identify firmware versions.
  • Check Insteon or vendor guidance for fixed firmware or replacement direction.
  • Restrict administrative access to trusted users and networks.
  • Rotate credentials for accounts able to control affected hubs.
  • Monitor for unusual authenticated hub-control activity.

Validation and detection

  • Confirm whether any deployed Insteon Hub runs firmware 1012.
  • Map which users or services can authenticate to each hub.
  • Review vendor advisories before attempting any security testing.
  • Validate exposure through configuration review, not crafted overflow traffic.
  • Check monitoring for unexpected PubNub-connected control activity.
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.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-16318 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
8.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/PR:L/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
8.5CVSS 3.0HighCVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H1.86Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.5High
CVSS 3.0 vector shape for CVE-2017-16318Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:H/PR:L/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
InsteonHubNot specifiedListed
Weakness

CWE details

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

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.