dbcve.org
Cc612 FirmwareOperating system · Bender

CVE-2021-34592

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
Remotely reachable 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 Command injection via Web interface. An authenticated attacker could enter shell commands into some input fields.

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

This is an OS command injection vulnerability in the web interface of Bender/ebee electric vehicle charge controllers. An authenticated attacker can inject arbitrary shell commands through insufficiently sanitized input fields in the web management interface, leading to remote code execution on the affected device.

MitigationUpdate to a patched firmware version provided by Bender. If no patch is available, restrict network access to the web management interface to trusted IP addresses only and ensure strong authentication credentials are used.

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

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

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 the device model
    Locate the charge controller model label on the physical device or check the web interface header for the model identifier (Cc612 or Icc15xx)
    Affected if The device is a Bender Cc612 or Icc15xx charge controller
  2. Determine the installed firmware version
    Access the web management interface and navigate to the system information or firmware version page, typically found under Settings or Status menus
    Affected if The firmware version falls within any of these ranges: 5.11.0 to 5.11.1, 5.12.0 to 5.12.4, 5.13.0 to 5.13.1, or 5.20.0 to 5.20.1
  3. Verify the web management interface is enabled
    Check the network configuration settings on the device to confirm the web interface HTTP/HTTPS service is active and listening
    Affected if The web management interface is accessible over the network (even on local LAN)
  4. Confirm authentication is required for the web interface
    Attempt to access the web interface without credentials or verify in the authentication settings that login is enforced for all pages
    Affected if The web interface accepts authentication credentials (the vulnerability requires valid authentication to exploit)

You are affected if you have a Bender Cc612 or Icc15xx charge controller running any firmware version between 5.11.0 and 5.11.1, 5.12.0 and 5.12.4, 5.13.0 and 5.13.1, or 5.20.0 and 5.20.1, with the web interface enabled and accessible to an attacker who can obtain valid credentials.

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

Update to a patched firmware version provided by Bender. If no patch is available, restrict network access to the web management interface to trusted IP addresses only and ensure strong authentication credentials are used.

Recommended fix High confidence

Upgrade to firmware version 5.11.2, 5.12.5, 5.13.2, or 5.20.2 (choose based on your current version branch)

  1. Identify the current firmware version of the Bender/ebee Charge Controller (Cc612 or Icc15xx) by accessing the device's web interface or administrative console
  2. Determine which version branch is currently installed (5.11.x, 5.12.x, 5.13.x, or 5.20.x)
  3. Download the appropriate fixed firmware version from the vendor's official support site or contact vendor for firmware files
  4. Schedule a maintenance window as firmware updates may require brief downtime
  5. Back up current device configuration if the web interface supports export/backup functionality
  6. Upload and install the fixed firmware version (5.11.2, 5.12.5, 5.13.2, or 5.20.2 depending on your branch)
  7. Verify the firmware update was successful by checking the web interface version display
  8. Confirm the device is functioning normally after the update
Caveat Review vendor release notes for any configuration changes or features that may require adjustment after upgrading

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

Fix this in Cc612 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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