{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3834 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3834 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3834 is a high-severity code injection vulnerability in Insteon Hub Firmware, published on 2 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-3834 and fix it if it is affected.\n\nWhat it is: CVE-2018-3834 is a high-severity code injection vulnerability in Insteon Hub Firmware, published on 2 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-3834 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-2018-3834/ (Markdown: https://insights.sbomify.com/CVE-2018-3834/index.md)","id":"CVE-2018-3834","markdown":"https://insights.sbomify.com/CVE-2018-3834/index.md","name":"CVE-2018-3834","record":{"aliases":["GHSA-9hrj-7j37-g424"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Insteon Hub","requires_auth":"none","summary":"An attacker can permanently brick the device by serving a valid but incompatible firmware image via a man-in-the-middle attack on the update channel.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"hub_firmware","vendor":"insteon"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"An exploitable permanent denial of service vulnerability exists in Insteon Hub running firmware version 1013. The firmware upgrade functionality, triggered via PubNub, retrieves signed firmware binaries using plain HTTP requests. The device doesn't check the kind of firmware image that is going to be installed and thus allows for flashing any signed firmware into any MCU. Since the device contains different and incompatible MCUs, flashing one firmware to the wrong MCU will result in a permanent brick condition. To trigger this vulnerability, an attacker needs to impersonate the remote server \"cache.insteon.com\" and serve a signed firmware image.","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":"Code injection in Insteon","id":"CVE-2018-3834","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"insteon:hub_firmware","products":["insteon:hub_firmware"],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Walt Disney Animation Studios PTEX","id":"CVE-2018-3835"},"packages":[],"prev":{"headline":"Security feature bypass in Insteon","id":"CVE-2018-3833"},"products":["Insteon"],"published":"2018-08-02","related":[{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Insteon"]},"summary":"An attacker can permanently brick the device by serving a valid but incompatible firmware image via a man-in-the-middle attack on the update channel.","url":"https://insights.sbomify.com/CVE-2018-3834/"}