dbcve.org
Hub FirmwareOperating system · Insteon

CVE-2017-16310

CRITICAL · 9.9 CVSS v3.1 Published 2023-01-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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_ch, at 0x9d01b7b0, the value for the `ch` 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stack-based buffer overflow in Insteon Hub firmware 1012's PubNub message handler for the 'cc' channel. The 'ch' key value from PubNub messages is copied using unsafe strcpy() into a 100-byte buffer at stack pointer offset $sp+0x334 without bounds checking, allowing overflow and arbitrary data overwrite when input exceeds 100 bytes. Requires authenticated HTTP request to trigger.

MitigationUpdate to patched firmware if available; otherwise implement input validation/length checks on PubNub message processing or deploy network-level filtering to restrict message sizes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hub FirmwareOperating system
Affected:= 1012

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device as an Insteon Hub
    Access the device's web interface or check the device model via its administrative console or API endpoint
    Affected if The device is an Insteon Hub model that supports firmware version 1012 and PubNub integration
  2. Determine the installed firmware version
    Check the firmware version through the device's web interface under Settings > Hub Info, or query the device's API for version information
    Affected if The firmware version is exactly 1012 (no other versions are affected)
  3. Verify PubNub messaging is enabled
    Check the device configuration for PubNub settings - look for PubNub subscription/publish keys and channel configuration in the web interface or device API
    Affected if PubNub is enabled and configured on the device (the vulnerability exists in the PubNub message handler)
  4. Confirm the cc channel exists in PubNub configuration
    Inspect the PubNub channel configuration on the device, specifically look for the 'cc' channel (likely related to device control/command channel)
    Affected if The 'cc' channel is present in the PubNub channel configuration

A user is affected if they have an Insteon Hub running firmware version 1012 with PubNub enabled and the cc channel configured for use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to patched firmware if available; otherwise implement input validation/length checks on PubNub message processing or deploy network-level filtering to restrict message sizes.

Recommended fix Moderate confidence

Insteon Hub firmware version greater than 1012 (contact Insteon for specific fixed release)

  1. 1. Identify the Insteon Hub device on the network that needs remediation
  2. 2. Access the Insteon Hub administrative interface or mobile application
  3. 3. Check the current firmware version under device settings
  4. 4. Navigate to the firmware update section and check for available updates
  5. 5. If a newer firmware version is available (greater than 1012), download and apply the update
  6. 6. Verify the firmware has been successfully updated and the device is functioning normally
  7. 7. After update, confirm the PubNub integration continues to work as expected
Caveat Firmware updates may temporarily disrupt Hub connectivity; ensure update is performed during maintenance window

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hub Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-16310 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-16310 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data