LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16311: 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 UpdateCheck, at 0x9d01bb64, the value for the `type` key is copied using `strcpy` to the buffer at `$sp+0x270`.This buffer is 16 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

This flaw affects Insteon Hub message handling and can let an authenticated attacker corrupt device memory. Successful exploitation could compromise confidentiality, integrity, and availability of the hub. The public source describes firmware version 1012, but broader version coverage and fixed-version information are incomplete.

Executive priority

Treat this as a high-priority IoT exposure where affected hubs support business operations or sit near trusted networks. Urgency is driven by high impact after authentication, not by confirmed active exploitation in the provided sources.

Technical view

CVE-2017-16311 is a stack-based buffer overflow in the Insteon Hub PubNub “cc” channel message handler. In the UpdateCheck command, the type key is copied into a 16-byte stack buffer using strcpy, allowing overwrite when oversized input is processed after an authenticated HTTP request.

Likely exposure

Exposure appears limited to Insteon Hub deployments matching the vulnerable firmware described by the source, especially firmware version 1012. The CVE affected-version metadata says versions are not specified, so teams should verify actual firmware inventory against vendor or Talos guidance.

Exploitation context

The source says exploitation requires specially crafted commands sent through PubNub and an authenticated HTTP request. There is no KEV listing in the provided bundle, and no cited source here states active exploitation in the wild.

Researcher notes

Key evidence is a Talos advisory describing a PubNub message handler overflow in firmware 1012. The bundle does not identify a patch, fixed version, or broad affected-version range. Avoid assuming active exploitation because KEV is false and no cited source supports it.

Mitigation direction

  • Inventory Insteon Hub devices and record firmware versions.
  • Check Insteon guidance for fixed firmware, replacement, or retirement options.
  • Prioritize firmware 1012 systems for remediation review.
  • Limit hub access to trusted users and accounts.
  • Isolate hubs from sensitive network segments where feasible.
  • Review monitoring for unexpected hub control activity.

Validation and detection

  • Confirm whether any Insteon Hub is deployed.
  • Compare firmware versions against the Talos report details.
  • Check whether exposed control paths require strong authentication.
  • Review logs for unusual authenticated hub control requests.
  • Document any compensating controls around affected hubs.
Prepared
Confidence
medium
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-16311 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-16311Attack 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.