Insteon Hub: 81 records in one advisory
81 records announced together, published 2023-01-11, every one of them citing the same advisory.
The advisory
Every record in this batch cites https://talosintelligence.com/vulnerability_reports/TALOS-2017-0483. That is the CNA's own reference, held in the index, and it is why these records are on one page.
What the records offer
No record in this batch publishes a fixed version in held sources.
No record in this batch is listed by CISA in held sources.
Every record names something of its own, listed against it below.
Most commonly mapped weakness across the batch: CWE-121: Stack-based Buffer Overflow.
What this page does not cover
This batch is 81 of the 84 records that cite the same advisory. The other 3 are different findings announced alongside it.
None of those 3 is grouped with any other. Each one has its own record page and nothing else.
The batch is what one advisory announced. It is not every record sharing this weakness, this product or this mechanism, and nothing here is scoped to any estate.
What this batch was researched, not held
Talos filed one Insteon Hub report and published 86 identifiers under it
Claudio Bozzato of Cisco Talos audited the Insteon Hub 2245-222 on firmware 1012. The record text these identifiers share is Talos's own, written as the assigning authority: multiple exploitable buffer overflow vulnerabilities exist in the PubNub message handler for the cc channel of Insteon Hub running firmware version 1012, and specially crafted commands sent through the PubNub service can cause a stack-based buffer overflow. Talos published that work as one report, TALOS-2017-0483, and gives the identifier range CVE-2017-16252 through CVE-2017-16337 under it, 86 numbers in all. Talos notified the vendor on 27 November 2017 and published on 19 June 2018, alongside eleven further Insteon Hub reports. In the blog post that accompanied them, Talos wrote that the majority of the vulnerabilities have their root cause in the unsafe usage of the strcpy function, and said firmware 1016 fixes the issues its reports cover. The identifiers only reached the public CVE list on 11 January 2023, more than five years after they were reserved on 31 October 2017.
Everything said here about a shared root cause is Talos speaking about its own report: Talos wrote that the majority of the vulnerabilities it covers come from unsafe use of strcpy, and Talos names firmware 1016 as the fix for what its reports cover. Those are statements about Talos's research and its wording, not a finding of ours that the records in this group are one flaw or that one update closes them. The identifiers were published together because Talos released them together, and each record stands on its own text.
The report does not map each identifier to the specific message parameter it belongs to, so a reader cannot work out which record describes which field, and Talos does not say whether real deployments were ever attacked this way. The vendor published nothing of its own that we could find, so the whole of this group's account comes from the researcher's side.
Written from talosintelligence.com, blog.talosintelligence.com, cveawg.mitre.org. Reviewed for whether every claim traces to one of them, by two independent graders, citation support 4.44 of 5, uniqueness 4 of 5. Stated at high confidence. Nothing in this box is a value the index holds, and none of it opens a receipt.
Listed for shared announcement, not shared vulnerability. Each record here is its own finding with its own page, and fixing one does not address another.
81 records, read from the index as it stood on 2026-09-20. Every row opens the record it names, and every value on that record opens its own receipt.