# CVE-2018-17614: Memory corruption in Losant Arduino MQTT Client

> Remote attackers can execute arbitrary code via stack-based buffer overflow in MQTT packet parsing without user interaction.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v2rq-3pp5-wf98

## What is CVE-2018-17614?

CVE-2018-17614 is a high-severity memory corruption vulnerability in Losant Arduino MQTT Client, published on 13 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Losant Arduino MQTT Client prior to V2.7. User interaction is not required to exploit this vulnerability. The specific flaw exists within the parsing of MQTT PUBLISH packets. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-6436.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2018-17614?

It affects 1 product.


Products: Losant Arduino Mqtt Client.

## How do I fix CVE-2018-17614?

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

## Is CVE-2018-17614 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17614 and fix it if it is affected.

What it is: CVE-2018-17614 is a high-severity memory corruption vulnerability in Losant Arduino MQTT Client, published on 13 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17614 in the wild and no public exploit code.

Affected product: Losant Arduino MQTT Client. 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-2018-17614/ (Markdown: https://insights.sbomify.com/CVE-2018-17614/index.md)
```

## Sources

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

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