CyberSecBulletin

Sungrowpower vulnerabilities

We track 8 vulnerabilities in Sungrowpower products across 2 products. 8 are rated high or critical, and none are known to be exploited. The most recent was published on February 26, 2025.

8vulnerabilities
5critical
3high
0exploited
8.8average CVSS score

Latest Sungrowpower vulnerabilities

  • 7.5 High severity

    Winet-s Firmware: Download of Code Without Integrity Check

    CVE-2024-50696Sungrowpower

    SunGrow WiNet-S V200.001.00.P025 and earlier versions is missing integrity checks for firmware upgrades. Sending a specific MQTT message allows an update to an inverter or a WiNet connectivity dongle with a bogus firmware file that is located on attacker-contr

  • 7.4 High severity

    Isolarcloud: Improper Certificate Validation

    CVE-2024-50691Sungrowpower

    SunGrow iSolarCloud Android app V2.1.6.20241104 and prior suffers from Missing SSL Certificate Validation. The app explicitly ignores certificate errors and is vulnerable to MiTM attacks. Attackers can impersonate the iSolarCloud server and communicate with th

  • 9.8 Critical severity

    Isolarcloud: Use of Hard-coded Credentials

    CVE-2024-50688Sungrowpower

    SunGrow iSolarCloud Android application V2.1.6.20241017 and prior contains hardcoded credentials. The application (regardless of the user account) and the cloud uses the same MQTT credentials for exchanging the device telemetry.

  • 9.1 Critical severity

    Isolarcloud: Authorization Bypass Through User-Controlled Key

    CVE-2024-50686Sungrowpower

    SunGrow iSolarCloud before the October 31, 2024 remediation is vulnerable to insecure direct object references (IDOR) via the commonService API model.

  • 9.1 Critical severity

    Isolarcloud: Authorization Bypass Through User-Controlled Key

    CVE-2024-50685Sungrowpower

    SunGrow iSolarCloud before the October 31, 2024 remediation, is vulnerable to insecure direct object references (IDOR) via the powerStationService API model.

  • 8.1 High severity

    Winet-s Firmware: Buffer Copy without Checking Size of Input

    CVE-2024-50697Sungrowpower

    In SunGrow WiNet-SV200.001.00.P027 and earlier versions, when decrypting MQTT messages, the code that parses specific TLV fields does not have sufficient bounds checks. This may result in a stack-based buffer overflow.

  • 9.8 Critical severity

    Winet-s Firmware: Stack-based Buffer Overflow

    CVE-2024-50695Sungrowpower

    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.

  • 9.8 Critical severity

    Winet-s Firmware: Stack-based Buffer Overflow

    CVE-2024-50694Sungrowpower

    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.