LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16268: 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_b, at 0x9d0165c0, the value for the `id` 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 can let an authenticated attacker crash or take control of an Insteon Hub by sending malformed cloud-delivered commands. The cited description specifically discusses firmware 1012. Business urgency is high where hubs control physical security, lighting, access, or safety-adjacent automation.

Executive priority

Treat this as high priority for any still-deployed Insteon Hub, especially in business-critical or physical-security workflows. The risk is not just device outage; successful exploitation could affect automation integrity and confidentiality. If vendor support is unclear, plan remediation around replacement or removal.

Technical view

CVE-2017-16268 is a stack-based buffer overflow in the Insteon Hub PubNub "cc" channel handler. The vulnerable code copies an overlong "id" value with strcpy into a 16-byte stack buffer, allowing arbitrary overwrite. CVSS 3.0 is 8.5 high with network reachability, low privileges, no user interaction, and changed scope.

Likely exposure

Exposure is most likely in environments still operating Insteon Hub devices matching the cited firmware context, especially firmware 1012. The source bundle does not prove all Hub versions are affected, and the CVE product version metadata says versions are not specified.

Exploitation context

The source says exploitation requires an authenticated HTTP request and specially crafted commands through PubNub. CISA KEV status is false in the bundle, and no cited source here claims active exploitation. Attack complexity is rated high, but impact is high across confidentiality, integrity, and availability.

Researcher notes

The bundle provides a specific vulnerable sink: strcpy copies the "id" key into a 16-byte stack buffer in cmd s_b. Avoid assuming broader firmware coverage beyond the cited firmware 1012 context. No patch, workaround, proof of exploitation, or KEV listing is provided in the supplied evidence.

Mitigation direction

  • Inventory Insteon Hub devices and identify firmware versions, especially firmware 1012.
  • Check Insteon or vendor guidance for fixed firmware, replacement, or retirement advice.
  • Limit Hub account and API access to trusted administrators only.
  • Rotate credentials for accounts authorized to send Hub commands.
  • Decommission or isolate affected hubs if no supported remediation exists.
  • Prioritize controls where hubs affect physical security or safety-adjacent automation.

Validation and detection

  • Confirm whether any deployed Insteon Hub runs firmware 1012.
  • Review asset records for Insteon Hub devices without known firmware versions.
  • Check administrative accounts authorized to send Hub commands.
  • Review cloud or account activity for unexplained Hub command activity.
  • Document whether vendor guidance names a fixed firmware or no supported fix.
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-16268 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-16268Attack 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.