dbcve.org
Winet S FirmwareOperating system · Sungrowpower

CVE-2024-50690

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 200.001.00.p027 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 WiNet-SV200.001.00.P027 and earlier versions contains a hardcoded password that can be used to decrypt all firmware updates.

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

SunGrow WiNet-SV200 devices (versions 001.00.P027 and earlier) contain a hardcoded password embedded in the firmware that serves as the decryption key for all firmware update packages. An attacker with knowledge of this password can decrypt any firmware update, analyze proprietary code, and potentially inject malicious modifications into firmware updates.

MitigationReplace the hardcoded decryption password with asymmetric encryption (e.g., RSA or ECDSA) and implement cryptographic code signing with public key verification before firmware installation. Until an official patch is available, verify firmware integrity through external channels before applying updates.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify device firmware version
    Access the WiNet-SV200 device management interface (web UI or CLI) and navigate to System Information or Firmware version settings to retrieve the current installed firmware version
    Affected if The displayed version is 001.00.P027 or earlier, or displays as less than 200.001.00.p027
  2. Compare version against affected range
    Compare your installed firmware version number to the known affected range: versions earlier than 200.001.00.p027
    Affected if Your installed version is numerically lower than 200.001.00.p027 (e.g., 001.00.P026, 001.00.P025, etc.)
  3. Obtain firmware update package
    Download the firmware update package from the official Sungrow support portal or device management system
    Affected if You are able to obtain firmware update files for this device
  4. Inspect firmware for hardcoded password
    Extract the firmware update package and search within the binary files for the hardcoded decryption key string (typically found in decryption/decryption utility code or configuration sections)
    Affected if A hardcoded password or key string is visible in plaintext within the firmware binary files

You are affected if your WiNet-SV200 device runs firmware version 001.00.P027 or earlier (below 200.001.00.p027), as these versions contain the hardcoded decryption password in the firmware.

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

Replace the hardcoded decryption password with asymmetric encryption (e.g., RSA or ECDSA) and implement cryptographic code signing with public key verification before firmware installation. Until an official patch is available, verify firmware integrity through external channels before applying updates.

Recommended fix Moderate confidence

200.001.00.p028 or later (any version newer than 200.001.00.p027 that contains the security fix)

  1. 1. Identify the current firmware version of the Winet S device by accessing the device management interface or checking the device documentation.
  2. 2. Navigate to the official SunGrow support website (en.sungrowpower.com) and locate the firmware download section for WiNet-S products.
  3. 3. Download the latest firmware version that is newer than 200.001.00.p027 - look for a version that specifically addresses security vulnerabilities including CWE-798.
  4. 4. Before applying the firmware update, back up any existing device configurations if the management interface supports this.
  5. 5. Apply the firmware update following the manufacturer's documented upgrade procedure, ensuring stable power supply during the process.
  6. 6. After the upgrade completes, verify the new firmware version is installed correctly.
  7. 7. If possible, change any default credentials that may have been hardcoded after the upgrade to further harden the device.
Caveat Review release notes for any configuration or compatibility changes between your current version and the new version before upgrading

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

Fix this in Winet S Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing10.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,660
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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