LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16299: 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_raw, at 0x9d01aad8, 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-16299 is a high-impact memory corruption flaw in Insteon Hub firmware 1012. A specially crafted authenticated request through PubNub can overflow a small stack buffer, potentially affecting confidentiality, integrity, and availability of the device.

Executive priority

Treat as high priority where Insteon Hub firmware 1012 is deployed, especially in environments where device compromise could affect physical operations or trusted networks. Prioritize inventory, access reduction, and vendor guidance review.

Technical view

The flaw is a CWE-121 stack-based buffer overflow in the PubNub message handler for the cc channel. In cmd sn_raw, the d key is copied with strcpy into a 100-byte stack buffer, allowing overflow when the value is longer than the buffer.

Likely exposure

Exposure appears limited to Insteon Hub devices running firmware version 1012 that process the affected PubNub cc channel command path. The source bundle does not specify broader affected versions.

Exploitation context

Sources describe network-reachable exploitation requiring an authenticated HTTP request and high attack complexity. The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation.

Researcher notes

Evidence is specific about the vulnerable copy operation and buffer size, but incomplete on patched versions, vendor-fixed firmware, and whether other firmware branches are affected. Avoid assuming exploitation in the wild from the supplied sources.

Mitigation direction

  • Identify Insteon Hub devices and confirm firmware versions.
  • Check Insteon and Talos guidance for firmware or replacement options.
  • Restrict authenticated access to the hub and related cloud-control path.
  • Segment affected hubs away from sensitive systems.
  • Review device accounts and remove unnecessary access.

Validation and detection

  • Inventory all Insteon Hub deployments and firmware versions.
  • Flag any device running firmware version 1012 for remediation review.
  • Review logs for unexpected authenticated requests involving PubNub control paths.
  • Confirm whether the cc channel command path is reachable in your environment.
  • Document compensating controls if vendor remediation is unavailable.
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-16299 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-16299Attack 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.