# CVE-2017-16252: Memory corruption in Insteon

> An authenticated attacker can trigger a stack-based buffer overflow in the Insteon Hub firmware via crafted PubNub commands, potentially leading to arbitrary code execution.

- **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:** 6 Aug 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-pqww-vj7p-6q2p

## What is CVE-2017-16252?

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

### Official description

Specially crafted commands sent through the PubNub service in Insteon Hub 2245-222 with firmware version 1012 can cause a stack-based buffer overflow overwriting arbitrary data. An attacker should send an authenticated HTTP request to trigger this vulnerability.At 0x9d014cc0 the value for the cmd key is copied using strcpy to the buffer at $sp+0x11c. This buffer is 20 bytes large, sending anything longer will cause a buffer overflow.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Insteon Hub Firmware.

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

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

## Is CVE-2017-16252 being exploited?

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

## Other vulnerabilities in Insteon Hub Firmware

- [CVE-2018-3834](https://insights.sbomify.com/CVE-2018-3834/): Code injection in Insteon (high 8.7)
- [CVE-2017-14454](https://insights.sbomify.com/CVE-2017-14454/): Memory corruption in Hub (high 8.5)
- [CVE-2017-16256](https://insights.sbomify.com/CVE-2017-16256/): Memory corruption in Hub (high 8.5)
- [CVE-2017-16257](https://insights.sbomify.com/CVE-2017-16257/): Memory corruption in Hub (high 8.5)
- [CVE-2017-16258](https://insights.sbomify.com/CVE-2017-16258/): Memory corruption in Hub (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16252 is a high-severity memory corruption vulnerability in Insteon Hub Firmware, published on 6 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-16252 in the wild and no public exploit code.

Affected product: Insteon Hub Firmware. 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-16252/ (Markdown: https://insights.sbomify.com/CVE-2017-16252/index.md)
```

## Sources

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

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