# CVE-2017-14455: Memory corruption in Insteon Hub 2245-222

> An attacker impersonating PubNub can trigger a buffer overflow via crafted replies, potentially leading to arbitrary code execution on the device.

- **Severity:** High 8.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-36xm-4j44-qpm8

## What is CVE-2017-14455?

CVE-2017-14455 is a high-severity memory corruption vulnerability in Insteon Hub 2245-222, published on 23 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On Insteon Hub 2245-222 devices with firmware version 1012, specially crafted replies received from the PubNub service can cause buffer overflows on a global section overwriting arbitrary data. An attacker should impersonate PubNub and answer an HTTPS GET request to trigger this vulnerability. A strcpy overflows the buffer insteon_pubnub.channel_ak, which has a size of 16 bytes. An attacker can send an arbitrarily long "ak" parameter in order to exploit this vulnerability.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-14455?

It affects 1 product.


Products: Insteon Hub 2245-222 Firmware.

## How do I fix CVE-2017-14455?

No fix has been published for CVE-2017-14455 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-14455 being exploited?

There is no known exploitation of CVE-2017-14455 in the wild and no public exploit code.

## Other vulnerabilities in Insteon Hub 2245-222

- [CVE-2018-3832](https://insights.sbomify.com/CVE-2018-3832/): File upload in Insteon (critical 9.9)
- [CVE-2017-14443](https://insights.sbomify.com/CVE-2017-14443/): Information disclosure in n/a (critical 9.6)
- [CVE-2018-3833](https://insights.sbomify.com/CVE-2018-3833/): Security feature bypass in Insteon (high 8.6)
- [CVE-2017-14453](https://insights.sbomify.com/CVE-2017-14453/): Memory corruption in Insteon Hub 2245-222 (high 8.5)
- [CVE-2017-16337](https://insights.sbomify.com/CVE-2017-16337/): Memory corruption in Insteon Hub 2245-222 (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14455 and fix it if it is affected.

What it is: CVE-2017-14455 is a high-severity memory corruption vulnerability in Insteon Hub 2245-222, published on 23 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14455 in the wild and no public exploit code.

Affected product: Insteon Hub 2245-222. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-14455/ (Markdown: https://insights.sbomify.com/CVE-2017-14455/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-14455
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-14455
- OSV: https://osv.dev/vulnerability/CVE-2017-14455

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-14455/
Summaries are generated and may contain mistakes; the official description above is the record.