{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16319 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16319 is a high-severity memory corruption vulnerability in Insteon Hub Firmware, published on 11 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16319 and fix it if it is affected.\n\nWhat it is: CVE-2017-16319 is a high-severity memory corruption vulnerability in Insteon Hub Firmware, published on 11 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-16319 in the wild and no public exploit code.\n\nAffected product: Insteon Hub Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-16319/ (Markdown: https://insights.sbomify.com/CVE-2017-16319/index.md)","id":"CVE-2017-16319","markdown":"https://insights.sbomify.com/CVE-2017-16319/index.md","name":"CVE-2017-16319","record":{"aliases":["GHSA-hw53-8r2v-h2g4"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Insteon Hub","requires_auth":"low_privilege","summary":"An attacker can trigger a stack-based buffer overflow in the Insteon Hub firmware via crafted PubNub commands, potentially leading to arbitrary code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"hub_firmware","vendor":"insteon"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"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 0x9d01d7a8, the value for the `g_sonos_index` key is copied using `strcpy` to the buffer at `$sp+0x1b4`.This buffer is 8 bytes large, sending anything longer will cause a buffer overflow.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in Hub","id":"CVE-2017-16319","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"insteon:hub_firmware","products":["insteon:hub_firmware"],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Hub","id":"CVE-2017-16320"},"packages":[],"prev":{"headline":"Memory corruption in Hub","id":"CVE-2017-16318"},"products":["Hub"],"published":"2023-01-11","related":[{"cvss_score":8.7,"headline":"Code injection in Insteon","id":"CVE-2018-3834","kev_date_added":null,"published":"2018-08-02"},{"cvss_score":8.5,"headline":"Memory corruption in Hub","id":"CVE-2017-14454","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":8.5,"headline":"Memory corruption in Hub","id":"CVE-2017-16256","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":8.5,"headline":"Memory corruption in Hub","id":"CVE-2017-16257","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":8.5,"headline":"Memory corruption in Hub","id":"CVE-2017-16258","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":8.5,"headline":"Memory corruption in Hub","id":"CVE-2017-16259","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":8.5,"headline":"Memory corruption in Hub","id":"CVE-2017-16260","kev_date_added":null,"published":"2023-01-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-08","vendors":["Insteon"]},"summary":"An attacker can trigger a stack-based buffer overflow in the Insteon Hub firmware via crafted PubNub commands, potentially leading to arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2017-16319/"}