# CVE-2019-5065: Information disclosure in Blynck Inc

> An attacker can send a crafted packet to trigger an unterminated strncpy, leading to information disclosure in the Blynk library.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gxh9-wgg7-4vx9

## What is CVE-2019-5065?

CVE-2019-5065 is a medium-severity vulnerability in Blynck Inc, published on 5 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable information disclosure vulnerability exists in the packet-parsing functionality of Blynk-Library v0.6.1. A specially crafted packet can cause an unterminated strncpy, resulting in information disclosure. An attacker can send a packet to trigger this vulnerability.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Blynk Blynk-Library.

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

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

## Is CVE-2019-5065 being exploited?

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

## Other vulnerabilities in Blynck Inc

- [CVE-2022-29496](https://insights.sbomify.com/CVE-2022-29496/): Memory corruption in Blynk-Library (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5065 is a medium-severity vulnerability in Blynck Inc, published on 5 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5065 in the wild and no public exploit code.

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

## Sources

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

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