dbcve.org
Hub FirmwareOperating system · Insteon

CVE-2017-16313

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_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.

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 's_ddelay' parameter is copied using unbounded strcpy to a 32-byte stack buffer at $sp+0x2b0, allowing overflow and potential arbitrary code execution when authenticated attackers send specially crafted commands exceeding 32 characters.

MitigationReplace strcpy with bounds-checked functions (strncpy, strlcpy) and validate input length before copying; update to patched firmware if available; network-segment devices to limit attack surface.

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 model
    Access the device's web interface or check the device label to confirm it is an Insteon Hub. The device model should be Insteon Hub with firmware version 1012.
    Affected if The device is an Insteon Hub running firmware version 1012 exactly.
  2. Determine firmware version
    Log into the Insteon Hub web interface (typically at 192.168.x.x) and navigate to Settings or About to view the firmware version. Alternatively, check the device packaging, documentation, or Insteon mobile app for the installed firmware version.
    Affected if The firmware version is exactly 1012.
  3. Check if PubNub integration is enabled
    Access the Insteon Hub settings via the web interface or mobile app and look for PubNub or cloud connectivity settings. Verify if the PubNub messaging service is configured or enabled.
    Affected if PubNub cloud messaging is enabled and connected.
  4. Verify network accessibility of the device
    Attempt to reach the Insteon Hub from an external network or confirm the device is reachable on the local network. Check if the device has port 443/80 open for web interface access.
    Affected if The device is network-accessible, allowing authenticated attackers to send commands.
  5. Confirm 'cc' channel existence
    Review the Insteon Hub API documentation or network traffic to identify if the 'cc' channel is present and active for PubNub messaging. This channel handles device control commands.
    Affected if The 'cc' PubNub channel is active and accessible to authenticated users.

A user is affected if they have an Insteon Hub running firmware version 1012 with PubNub integration enabled and the 'cc' channel accessible to authenticated attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace strcpy with bounds-checked functions (strncpy, strlcpy) and validate input length before copying; update to patched firmware if available; network-segment devices to limit attack surface.

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-16313 — 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-16313 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