dbcve.org
Cc612 FirmwareOperating system · Bender

CVE-2021-34588

HIGH · 8.6 CVSS v3.1 Published 2022-04-27
Fix available
A fix is available. Upgrade to 5.11.2 / 5.12.5 or later.
See remediation →
95/100
Remediation priority · Urgent
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
In Bender/ebee Charge Controllers in multiple versions are prone to unprotected data export. Backup export is protected via a random key. The key is set at user login. It is empty after reboot .

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

Bender/ebee Charge Controllers contain an unprotected data export vulnerability where backup exports are theoretically protected by a random key, but this key is only set upon user login and becomes empty after device reboot, leaving sensitive backup data exposed without authentication.

MitigationEnsure backup exports cannot be performed until a new random key has been properly established after reboot; implement persistent key storage or alternative authentication mechanism to maintain protection across reboots.

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
Cc612 FirmwareOperating system
Affected:>= 5.11.0, < 5.11.2>= 5.12.0, < 5.12.5>= 5.13.0, < 5.13.2>= 5.20.0, < 5.20.2
Icc15xx FirmwareOperating system
Affected:>= 5.11.0, < 5.11.2>= 5.12.0, < 5.12.5>= 5.13.0, < 5.13.2>= 5.20.0, < 5.20.2

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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 device firmware version
    Access the Bender CC612 or ICC15xx web interface or system status page to view the installed firmware version. This is typically found under Settings > System Info or a similar administrative page.
    Affected if The installed firmware version falls within any of these ranges: >= 5.11.0 and < 5.11.2; >= 5.12.0 and < 5.12.5; >= 5.13.0 and < 5.13.2; >= 5.20.0 and < 5.20.2
  2. Confirm device has been rebooted
    Check the device uptime since last reboot. This can be done via the web interface status page, system logs, or by accessing the device's command line interface if available.
    Affected if The device has been rebooted and no user has logged in afterward to establish a new random protection key
  3. Attempt unauthenticated backup export access
    Attempt to access the backup export function or endpoint without providing any authentication credentials. Try accessing the typical backup export URL path such as /backup, /export, or similar export-related endpoints without logging in.
    Affected if The backup export is accessible without requiring authentication, indicating the protection key is empty after reboot
  4. Verify backup contains sensitive data
    If backup export is accessible, examine the downloaded backup file to confirm it contains sensitive configuration or operational data.
    Affected if The exported backup file contains sensitive information such as user credentials, system configurations, or operational settings

You are affected if your device runs an affected firmware version (within the specified ranges) AND has been rebooted without a subsequent user login, allowing unauthenticated access to sensitive backup exports.

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 5.11.2 / 5.12.5 / 5.13.2 or later
Fixed in 5.11.25.12.55.13.2
Interim mitigation

Ensure backup exports cannot be performed until a new random key has been properly established after reboot; implement persistent key storage or alternative authentication mechanism to maintain protection across reboots.

Recommended fix High confidence

Firmware version 5.20.2 or later (or 5.11.2/5.12.5/5.13.2 for respective version branches)

  1. Identify the current firmware version of the Bender/ebee Charge Controller (Cc612 or Icc15xx) by accessing the device management interface
  2. Navigate to the firmware update section in the device administration panel
  3. Upgrade the firmware to version 5.20.2 or later (recommended)
  4. Alternatively, upgrade to 5.11.2, 5.12.5, or 5.13.2 depending on your current major version branch
  5. After upgrading, verify that the backup export protection functions correctly and persists after reboot
  6. Confirm the random key is properly set and maintained after device restart

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

Fix this in Cc612 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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