# CVE-2019-5039: Memory corruption in Nest Labs

> A heap-based buffer overflow in OpenWeave allows remote code execution via a crafted certificate, impacting Nest Labs IoT devices.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mqw2-4hpp-cmw6

## What is CVE-2019-5039?

CVE-2019-5039 is a high-severity memory corruption vulnerability in Nest Labs, published on 20 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An exploitable command execution vulnerability exists in the ASN1 certificate writing functionality of Openweave-core version 4.0.2. A specially crafted weave certificate can trigger a heap-based buffer overflow, resulting in code execution. An attacker can craft a weave certificate to trigger this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2019-5039?

It affects 1 product.


Products: Openweave Openweave-Core.

## How do I fix CVE-2019-5039?

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

## Is CVE-2019-5039 being exploited?

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

## Other vulnerabilities in Nest Labs

- [CVE-2019-5038](https://insights.sbomify.com/CVE-2019-5038/): Memory corruption in Nest Labs (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5039 and fix it if it is affected.

What it is: CVE-2019-5039 is a high-severity memory corruption vulnerability in Nest Labs, published on 20 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-5039 in the wild and no public exploit code.

Affected product: Nest Labs. 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-2019-5039/ (Markdown: https://insights.sbomify.com/CVE-2019-5039/index.md)
```

## Sources

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

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