dbcve.org
Winet S FirmwareOperating system · Sungrowpower

CVE-2024-50694

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 200.001.00.p027 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In SunGrow WiNet-SV200.001.00.P027 and earlier versions, when copying the timestamp read from an MQTT message, the underlying code does not check the bounds of the buffer that is used to store the message. This may lead to a stack-based buffer overflow.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stack-based buffer overflow vulnerability in SunGrow WiNet-SV200 firmware versions 001.00.P027 and earlier. When copying a timestamp from incoming MQTT messages, the code fails to validate buffer size bounds before writing data, allowing overflow of the stack buffer via a specially crafted MQTT message with an oversized timestamp field.

MitigationApply vendor firmware update when available; as interim measures, restrict network exposure of the MQTT interface, implement network segmentation, and monitor for anomalous MQTT traffic patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Winet S FirmwareOperating system
Affected:< 200.001.00.p027

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the SunGrow WiNet-SV200 device
    Locate the device model number on the physical device label, in the web management interface under Device Information, or via SNMP/sysinfo queries. Confirm the model is WiNet-SV200.
    Affected if The device is not a WiNet-SV200 model.
  2. Check the installed firmware version
    Access the device web UI, navigate to System > Firmware Version or Device Information page. Record the firmware version number displayed. Alternatively, check via CLI if SSH/Telnet access is available using 'show version' or 'version' commands.
    Affected if The firmware version is 001.00.P027 or earlier, or any version below 200.001.00.p027.
  3. Verify if MQTT service is enabled
    Access the device configuration interface, typically under Settings > Communication > MQTT, or Settings > Network > Protocol Settings. Check if MQTT client or MQTT broker is turned on. Look for MQTT broker/listener status.
    Affected if MQTT is disabled or not configured on the device.
  4. Check MQTT network exposure
    Perform a network port scan targeting the device IP on ports 1883 (MQTT) and 8883 (MQTTS). Review firewall rules and network ACLs protecting the device. Check if the device MQTT port is reachable from untrusted networks.
    Affected if The MQTT port (1883/8883) is accessible from outside the trusted network or directly from the internet.

The environment is affected if a SunGrow WiNet-SV200 device runs firmware version 001.00.P027 or earlier AND has MQTT enabled and network accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 200.001.00.p027 or later
Fixed in 200.001.00.p027
Interim mitigation

Apply vendor firmware update when available; as interim measures, restrict network exposure of the MQTT interface, implement network segmentation, and monitor for anomalous MQTT traffic patterns.

Recommended fix High confidence

200.001.00.p027

  1. 1. Download the WiNet-S firmware version 200.001.00.p027 or later from SunGrow's official support portal at en.sungrowpower.com
  2. 2. Review the firmware upgrade instructions provided by SunGrow for the WiNet-S device
  3. 3. Apply the firmware update following the vendor's recommended procedure
  4. 4. Verify the firmware has been successfully updated to version 200.001.00.p027 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Winet S Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-50694 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data