dbcve.org
IsolarcloudApplication · Sungrowpower

CVE-2024-50691

HIGH · 7.4 CVSS v3.1 Published 2025-02-26
Fix available
A fix is available. Upgrade to 2.1.6.20241115 or later.
See remediation →
83/100
Remediation priority · High
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.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.

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 · high confidence

The SunGrow iSolarCloud Android app V2.1.6.20241104 and prior fails to validate SSL/TLS certificates, explicitly ignoring certificate errors. This allows attackers on the same network to perform Man-in-the-Middle attacks, impersonate the iSolarCloud server, intercept communications, and potentially inject malicious responses into the app's data stream.

MitigationImplement proper SSL certificate validation in the app by removing code that ignores certificate errors and using a properly configured TrustManager or certificate pinning to ensure the app only trusts legitimate iSolarCloud server certificates.

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.20241115

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
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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. Check installed iSolarCloud app version
    On the Android device, go to Settings > Apps > iSolarCloud (or Sungrowpower Isolarcloud) > App info. Note the version number displayed under the app name.
    Affected if The displayed version is V2.1.6.20241104 or any version earlier than 2.1.6.20241115
  2. Verify version number format
    Confirm the exact version string shown in the app's 'About' or 'Version' section within the app settings menu.
    Affected if The version string is less than 2.1.6.20241115 when compared lexicographically or numerically
  3. Check APK package version if APK available
    If you have access to the APK file, use a tool like 'aapt dump badging' or APK info apps to extract the versionName and versionCode attributes.
    Affected if The versionName is 2.1.6.20241104 or prior, or versionCode is lower than the build corresponding to 2.1.6.20241115

You are affected if any device in your environment has the iSolarCloud app installed with version 2.1.6.20241104 or earlier (any version below 2.1.6.20241115), since these versions explicitly ignore SSL/TLS certificate validation errors.

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.20241115 or later
Fixed in 2.1.6.20241115
Interim mitigation

Implement proper SSL certificate validation in the app by removing code that ignores certificate errors and using a properly configured TrustManager or certificate pinning to ensure the app only trusts legitimate iSolarCloud server certificates.

Recommended fix Moderate confidence

Isolarcloud version 2.1.6.20241115 or later

  1. Ensure your Android device is connected to a trusted network
  2. Open Google Play Store and search for "iSolarCloud" by Sungrow
  3. Update the iSolarCloud app to the latest available version
  4. Alternatively, visit en.sungrowpower.com and download the latest iSolarCloud Android app from the official download section
  5. Verify the updated app version is 2.1.6.20241115 or later
  6. After updating, log in to the app and confirm normal functionality

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

Fix this in Isolarcloud Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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