LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16313: 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 0x9d01c084, the value for the `s_ddelay` 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-16313 is a high-severity memory corruption flaw in Insteon Hub firmware 1012. An authenticated attacker could send crafted PubNub commands that overflow a small stack buffer, potentially affecting confidentiality, integrity, and availability. The source bundle does not show confirmed active exploitation or a named patch.

Executive priority

Treat this as a high-priority asset validation issue, not a broad emergency. The business risk is highest where Insteon Hubs remain deployed, cloud-connected, and reachable by accounts that may be weakly controlled. Confirm exposure and vendor remediation status promptly.

Technical view

The issue is a CWE-121 stack-based buffer overflow in the PubNub cc channel handler. In cmd s_sonos, the s_ddelay value is copied with strcpy into a 32-byte stack buffer. Oversized authenticated input can overwrite stack data. CVSS 3.0 is 8.5 with network attack vector, low privileges, high complexity, and no user interaction.

Likely exposure

Exposure appears limited to Insteon Hub deployments running firmware version 1012, especially where the Hub processes PubNub cc channel commands. The affected versions field is not fully specified, so teams should verify actual firmware and vendor status rather than assuming only one build is relevant.

Exploitation context

The CVE states exploitation requires an authenticated HTTP request and specially crafted commands sent through PubNub. KEV status is false, and the provided sources do not claim active exploitation. High attack complexity and required low privileges reduce opportunistic risk but do not remove concern for exposed or compromised accounts.

Researcher notes

The strongest technical evidence is Talos reporting a strcpy copy of s_ddelay into a 32-byte stack buffer in cmd s_sonos. The bundle lacks patch details, exploit-in-the-wild claims, and complete affected-version metadata. Avoid broad product conclusions beyond Insteon Hub firmware 1012.

Mitigation direction

  • Inventory Insteon Hub devices and identify firmware versions in use.
  • Check Insteon or vendor guidance for fixed firmware or retirement advice.
  • Restrict Hub administration and cloud-linked access to trusted accounts only.
  • Segment affected devices from sensitive networks where operationally possible.
  • Monitor for unusual authenticated Hub or PubNub-related activity.

Validation and detection

  • Confirm whether any Insteon Hub is running firmware version 1012.
  • Review whether PubNub-connected Hub functionality is enabled or required.
  • Verify who can send authenticated requests affecting the Hub.
  • Check vendor advisories before declaring the device remediated.
  • Document compensating controls for any Hub that cannot be updated.
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-16313 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-16313Attack 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.