dbcve.org
IsolarcloudApplication · Sungrowpower

CVE-2024-50684

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-26
Fix available
A fix is available. Upgrade to 2.1.6.20241104 or later.
See remediation →
74/100
Remediation priority · Elevated
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
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.

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

The SunGrow iSolarCloud Android app versions V2.1.6.20241017 and prior implements AES encryption using a cryptographically weak key with insufficient entropy. This allows an attacker who can intercept network traffic (e.g., via man-in-the-middle attack) to recover the encryption key and decrypt sensitive communications between the mobile app and iSolarCloud backend.

MitigationUpdate the iSolarCloud Android app to a version beyond V2.1.6.20241017 that implements proper AES key generation with sufficient entropy, or replace the hardcoded/weak key with securely generated cryptographic keys.

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
IsolarcloudApplication
Affected:< 2.1.6.20241104

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

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. Locate iSolarCloud app on Android device
    Open Android Settings > Apps > iSolarcloud or Sungrowpower Isolarcloud. If not present, the app is not installed.
    Affected if App is installed and version is below 2.1.6.20241104
  2. Check installed app version
    In Settings > Apps > iSolarcloud, view the Version or Version Name field under App Info.
    Affected if Version displayed is V2.1.6.20241017 or earlier, or any version number less than 2.1.6.20241104
  3. Verify app uses network communication
    The iSolarCloud app inherently connects to iSolarCloud backend for monitoring/control. Check in Settings > Apps > iSolarcloud > Mobile Data that network access is enabled.
    Affected if App communicates with iSolarCloud servers and uses the weak AES encryption for that traffic
  4. Confirm version via Play Store if available
    Open Google Play Store, search for iSolarCloud or Sungrowpower Isolarcloud, and view the current version in the app listing.
    Affected if Play Store shows a version prior to 2.1.6.20241104 as the latest installed version

You are affected if the iSolarCloud Android app is installed with version 2.1.6.20241017 or earlier (or version below 2.1.6.20241104) and it communicates with the iSolarCloud backend.

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 2.1.6.20241104 or later
Fixed in 2.1.6.20241104
Interim mitigation

Update the iSolarCloud Android app to a version beyond V2.1.6.20241017 that implements proper AES key generation with sufficient entropy, or replace the hardcoded/weak key with securely generated cryptographic keys.

Recommended fix High confidence

2.1.6.20241104 or later

  1. 1. Open the Google Play Store (Android) or Apple App Store (iOS) on your mobile device
  2. 2. Search for "iSolarCloud" or "SunGrow" in the app store
  3. 3. Check the current installed version of the iSolarCloud app in your device settings under Apps > iSolarCloud > Version
  4. 4. If an update is available, tap "Update" to install version 2.1.6.20241104 or later
  5. 5. Alternatively, visit en.sungrowpower.com and navigate to the download section for the iSolarCloud mobile app to obtain the latest version
  6. 6. After updating, verify the app version shows 2.1.6.20241104 or higher under Apps > iSolarCloud > Version

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

Fix this in Isolarcloud Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50684 — 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-50684 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