# CVE-2024-50695: Memory corruption in n/a

> Attackers can trigger a stack-based buffer overflow via crafted MQTT messages, potentially leading to code execution or denial of service on SunGrow WiNet devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2025
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-jg2r-v58r-q7vh

## What is CVE-2024-50695?

CVE-2024-50695 is a critical memory corruption vulnerability in n/a, published on 24 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SunGrow WiNet-SV200.001.00.P027 and earlier versions is vulnerable to stack-based buffer overflow when parsing MQTT messages, due to missing MQTT topic bounds checks.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2024-50695?

It affects 1 product.


Products: Sungrowpower Winet-S Firmware.

## How do I fix CVE-2024-50695?

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

## Is CVE-2024-50695 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-50694](https://insights.sbomify.com/CVE-2024-50694/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-50698](https://insights.sbomify.com/CVE-2024-50698/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-50697](https://insights.sbomify.com/CVE-2024-50697/): Memory corruption in n/a (high 8.1)
- [CVE-2024-50696](https://insights.sbomify.com/CVE-2024-50696/): Supply chain in n/a (high 7.5)
- [CVE-2024-50690](https://insights.sbomify.com/CVE-2024-50690/): Hardcoded credentials in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50695 and fix it if it is affected.

What it is: CVE-2024-50695 is a critical memory corruption vulnerability in n/a, published on 24 Jan 2025. 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-2024-50695 in the wild and no public exploit code.

Affected product: n/a. 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-2024-50695/ (Markdown: https://insights.sbomify.com/CVE-2024-50695/index.md)
```

## Sources

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

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