CVE-2021-34602
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 · uneditedIn 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 that are executed with root privileges.
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 confidenceOS command injection vulnerability in Bender/ebee Charge Controllers web interface allows authenticated attackers to execute arbitrary shell commands with root privileges through unsanitized input fields.
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>= 5.11.0, < 5.11.2>= 5.12.0, < 5.12.5>= 5.13.0, < 5.13.2>= 5.20.0, < 5.20.2>= 5.11.0, < 5.11.2>= 5.12.0, < 5.12.5>= 5.13.0, < 5.13.2>= 5.20.0, < 5.20.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device web interface or check the device label/documentation to confirm it is a Bender CC612 or Icc15xx Charge ControllerAffected if Device is not a Bender CC612 or Icc15xx, then not affected by this CVE
-
Check the installed firmware versionLog into the web interface and navigate to the system information or firmware version page; alternatively, check via the device console or documentation provided by the administratorAffected if Firmware version falls within any of these ranges: >= 5.11.0 and < 5.11.2, OR >= 5.12.0 and < 5.12.5, OR >= 5.13.0 and < 5.13.2, OR >= 5.20.0 and < 5.20.2
-
Review web interface user accountsCheck the device user management section to determine if default or weak credentials are in use, and review for any unauthorized accountsAffected if Default credentials are unchanged or unauthorized user accounts exist, indicating potential prior exploitation
The environment is affected if the device is a Bender CC612 or Icc15xx with firmware version matching any of the affected ranges AND the web interface is accessible to attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.11.25.12.55.13.2
Apply vendor-provided firmware patches when available; until then, restrict web interface access to trusted networks only, disable remote management if possible, and monitor for indicators of compromise.
Upgrade to firmware version 5.20.2 (or latest 5.x.x stable release >= 5.20.2)
- Identify the current firmware version of the affected Bender/ebee Charge Controller (Cc612 or Icc15xx)
- Download the appropriate fixed firmware version from the vendor (Bender/ebee)
- Review vendor documentation for firmware upgrade procedures
- Back up current configuration if supported by the device
- Upload and install the fixed firmware version (5.11.2, 5.12.5, 5.13.2, or 5.20.2)
- Verify the upgrade was successful and the device is functioning normally
- Confirm the vulnerability is remediated by checking the firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34602 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-34602 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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