LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16333: 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_event, at 0x9d01ed7c, the value for the `s_offset` 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 devices and could let an authenticated attacker crash or potentially take over a vulnerable hub. The public record names firmware 1012 in the technical description, but product version coverage is otherwise incomplete. No provided source reports active exploitation.

Executive priority

Treat this as high priority where Insteon Hubs remain deployed. It is not supported as an active-exploitation emergency by the supplied evidence, but the potential confidentiality, integrity, and availability impact is severe.

Technical view

Talos describes stack-based buffer overflows in the Insteon Hub PubNub message handler for the cc channel. In cmd s_event, the s_offset value is copied with strcpy into a 32-byte stack buffer, enabling overwrite of stack data when an authenticated HTTP request reaches the vulnerable handler.

Likely exposure

Likely limited to environments still operating Insteon Hub devices, especially firmware version 1012. The source bundle does not confirm all affected versions, supported firmware status, or whether newer hubs are impacted.

Exploitation context

The CVSS vector is network reachable with low privileges, no user interaction, high impact, and high attack complexity. The attacker must be authenticated. KEV is false, and the supplied sources do not state that exploitation is occurring in the wild.

Researcher notes

Evidence is strongest for firmware 1012 and the Talos-described cc channel handler. The affected version range and patch status are incomplete in the provided bundle, so validation should focus on asset presence, firmware state, authentication exposure, and vendor advisories.

Mitigation direction

  • Inventory Insteon Hub devices and record firmware versions.
  • Check Insteon or vendor guidance for firmware updates, mitigations, or retirement advice.
  • Limit authenticated control access to trusted administrators only.
  • Review whether PubNub-based hub control is required in production.
  • Retire or isolate unsupported hubs if no vendor fix is available.

Validation and detection

  • Confirm whether any deployed Insteon Hub runs firmware 1012.
  • Verify who can authenticate to the hub control path.
  • Review device logs for unexpected authenticated control activity.
  • Confirm whether vendor guidance identifies a fixed firmware version.
  • Document any hubs that cannot be patched or replaced.
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-16333 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-16333Attack 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.