Filtered by vendor Sungrowpower Subscriptions
Filtered by product Isolarcloud Subscriptions
Total 8 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2024-50684 1 Sungrowpower 1 Isolarcloud 2025-04-07 6.5 Medium
SunGrow iSolarCloud Android app V2.1.6.20241017 and prior uses an insecure AES key to encrypt client data (insufficient entropy). This may allow attackers to decrypt intercepted communications between the mobile app and iSolarCloud.
CVE-2024-50685 1 Sungrowpower 1 Isolarcloud 2025-04-07 9.1 Critical
SunGrow iSolarCloud before the October 31, 2024 remediation, is vulnerable to insecure direct object references (IDOR) via the powerStationService API model.
CVE-2024-50686 1 Sungrowpower 1 Isolarcloud 2025-04-07 9.1 Critical
SunGrow iSolarCloud before the October 31, 2024 remediation is vulnerable to insecure direct object references (IDOR) via the commonService API model.
CVE-2024-50687 1 Sungrowpower 1 Isolarcloud 2025-04-07 9.1 Critical
SunGrow iSolarCloud before the October 31, 2024 remediation is vulnerable to insecure direct object references (IDOR) via the devService API model.
CVE-2024-50688 1 Sungrowpower 1 Isolarcloud 2025-04-07 9.8 Critical
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.
CVE-2024-50689 1 Sungrowpower 1 Isolarcloud 2025-04-07 9.1 Critical
SunGrow iSolarCloud before the October 31, 2024 remediation is vulnerable to insecure direct object references (IDOR) via the orgService API model.
CVE-2024-50691 1 Sungrowpower 1 Isolarcloud 2025-04-07 7.4 High
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 the Android app.
CVE-2024-50693 1 Sungrowpower 1 Isolarcloud 2025-04-07 9.1 Critical
SunGrow iSolarCloud before the October 31, 2024 remediation is vulnerable to insecure direct object references (IDOR) via the userService API model.