LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16304: 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 sn_ex, at 0x9d01ae40, the value for the `d` key is copied using `strcpy` to the buffer at `$sp+0x334`.This buffer is 100 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-16304 is a high-severity memory corruption flaw in Insteon Hub firmware 1012. An authenticated attacker could send crafted PubNub-linked commands that overflow a stack buffer, potentially affecting confidentiality, integrity, and availability. Public sources do not confirm active exploitation or a specific vendor fix.

Executive priority

Treat this as a high-priority IoT exposure if Insteon Hubs are deployed, especially on sensitive networks. Prioritize inventory, segmentation, and vendor remediation checks over emergency incident response unless local telemetry indicates suspicious activity.

Technical view

The issue is a CWE-121 stack-based buffer overflow in the PubNub "cc" channel message handler. In cmd sn_ex, the d key is copied with strcpy into a 100-byte stack buffer, allowing oversized input to overwrite adjacent data. CVSS 3.0 is 8.5 with network attack vector, high complexity, low privileges, and no user interaction.

Likely exposure

Confirmed exposure is Insteon Hub running firmware version 1012. The supplied affected-version metadata is otherwise unspecified, so exposure beyond firmware 1012 is not established by the provided sources.

Exploitation context

The CVE is not listed as KEV in the supplied data, and no cited source states active exploitation. Exploitation requires an authenticated HTTP request and crafted commands through the PubNub service, with high attack complexity but potentially severe impact.

Researcher notes

Key evidence comes from Talos and CVE data. The vulnerable operation is strcpy of the d key into a 100-byte stack buffer in cmd sn_ex. Sources do not provide exploit-in-the-wild evidence, patch status, or confirmed affected versions beyond firmware 1012.

Mitigation direction

  • Identify Insteon Hubs and verify firmware versions, especially version 1012.
  • Check Insteon or Talos guidance before assuming a fixed firmware exists.
  • Isolate IoT hubs from sensitive corporate and production networks.
  • Restrict management access to trusted users and trusted network paths.
  • Replace unsupported hubs if no vendor-supported remediation is available.

Validation and detection

  • Inventory deployed Insteon Hub devices and record firmware versions.
  • Confirm whether any hub is running firmware version 1012.
  • Review authentication controls for hub management and PubNub-linked command paths.
  • Check monitoring for unusual authenticated hub control activity.
  • Avoid destructive overflow testing on 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.

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-16304 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-16304Attack 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.