LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16288: 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_time, at 0x9d018f60, the value for the `dst` 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

This CVE affects Insteon Hub firmware 1012. A flaw in cloud-delivered command handling can let an authenticated attacker crash or potentially take control of the hub by overflowing a small memory buffer. The sources do not state that exploitation is active or that a patch exists.

Executive priority

Treat as high priority where Insteon Hubs are deployed in business-critical or security-sensitive spaces. The practical urgency depends on whether affected hubs exist, whether authenticated access is tightly controlled, and whether vendor remediation is available.

Technical view

The PubNub "cc" channel handler in Insteon Hub firmware 1012 contains a stack-based buffer overflow. In the cmd s_time path, the `dst` value is copied with `strcpy` into a 32-byte stack buffer. CVSS 3.0 is 8.5, with network access, low privileges, high complexity, no user interaction, and high CIA impact.

Likely exposure

Exposure is likely limited to environments running Insteon Hub devices, especially firmware version 1012. The affected versions field is incomplete, so vulnerability managers should not assume other firmware versions are safe without vendor confirmation.

Exploitation context

The source states an attacker must send an authenticated HTTP request that results in crafted commands through PubNub. CISA KEV is false in the bundle, and no cited source confirms active exploitation.

Researcher notes

Evidence is strongest for firmware 1012 and the `dst` handling path described by Talos. The affected-version metadata is incomplete, and the bundle does not include exploit-in-the-wild evidence or remediation details.

Mitigation direction

  • Inventory Insteon Hub deployments and identify firmware versions.
  • Check current Insteon or vendor guidance for fixed firmware or replacement advice.
  • Reduce access to hub management and cloud-control paths until remediated.
  • Rotate or review credentials that can issue authenticated hub requests.
  • Monitor for unusual authenticated command activity involving affected hubs.

Validation and detection

  • Confirm whether any Insteon Hub is running firmware 1012.
  • Record hub model, firmware, network placement, and cloud connectivity status.
  • Review logs for unexpected authenticated hub control activity.
  • Do not validate by triggering buffer overflow behavior in production.
  • Track vendor advisories because the source bundle names no patch.
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-16288 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-16288Attack 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.