# CVE-2022-29496: Memory corruption in Blynk-Library

> A stack-based buffer overflow in the Blynk library allows remote attackers to execute arbitrary commands via a specially crafted network request.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-4v52-cfm2-5xvm

## What is CVE-2022-29496?

CVE-2022-29496 is a critical memory corruption vulnerability in Blynk-Library, published on 17 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack-based buffer overflow vulnerability exists in the BlynkConsole.h runCommand functionality of Blynk -Library v1.0.1. A specially-crafted network request can lead to command execution. An attacker can send a network request to trigger this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2022-29496?

It affects 1 product.


Products: Blynk Blynk-Library.

## How do I fix CVE-2022-29496?

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

## Is CVE-2022-29496 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29496 exists.

## Other vulnerabilities in Blynk-Library

- [CVE-2019-5065](https://insights.sbomify.com/CVE-2019-5065/): Information disclosure in Blynck Inc (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29496 and fix it if it is affected.

What it is: CVE-2022-29496 is a critical memory corruption vulnerability in Blynk-Library, published on 17 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29496 exists.

Affected product: Blynk-Library. 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-2022-29496/ (Markdown: https://insights.sbomify.com/CVE-2022-29496/index.md)
```

## Sources

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

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