dbcve.org
Cc612 FirmwareOperating system · Bender

CVE-2021-34591

HIGH · 7.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 →
80/100
Remediation priority · High
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 Local privilege Escalation. An authenticated attacker could get root access via the suid applications socat, ip udhcpc and ifplugd.

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

Local privilege escalation vulnerability in Bender/ebee Charge Controllers where authenticated attackers can gain root access by exploiting SUID binaries (socat, ip/udhcpc, ifplugd) that have insecure permissions or can be leveraged to execute arbitrary code with elevated privileges.

MitigationRemove unnecessary SUID bits from socat, ip, udhcpc, and ifplugd binaries or update to vendor-patched versions; follow least-privilege principles and restrict device authentication.

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

CVSS:3.1/AV:L/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 device model and firmware version
    Access the device admin interface or use the command line to retrieve the model (Cc612 or Icc15xx) and firmware version. Look for version information in /etc/version, the web UI about page, or via 'show version' CLI command.
    Affected if The device is a Bender Cc612 or Icc15xx and the firmware version falls within: 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.
  2. Check for socat binary with SUID bit
    Run 'ls -la /usr/bin/socat' or 'find / -name socat -perm -4000 2>/dev/null' to locate the socat binary and verify if the SUID bit is set.
    Affected if The socat binary exists and has the SUID bit set (permissions show 'rwsr-xr-x' or similar).
  3. Check for ip or udhcpc binary with SUID bit
    Run 'ls -la /bin/ip' or 'ls -la /usr/sbin/ip' and 'ls -la /bin/udhcpc' or 'ls -la /usr/sbin/udhcpc' to check if these binaries exist with SUID permissions.
    Affected if The ip binary or udhcpc binary exists and has the SUID bit set (permissions show 'rwsr-xr-x' or similar).
  4. Check for ifplugd binary with SUID bit
    Run 'ls -la /usr/sbin/ifplugd' or 'find / -name ifplugd -perm -4000 2>/dev/null' to locate the ifplugd binary and verify if the SUID bit is set.
    Affected if The ifplugd binary exists and has the SUID bit set (permissions show 'rwsr-xr-x' or similar).

A device is affected if it is a Bender Cc612 or Icc15xx running a vulnerable firmware version AND one or more of the binaries (socat, ip/udhcpc, ifplugd) have the SUID bit set, allowing an authenticated attacker to escalate privileges to root.

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

Remove unnecessary SUID bits from socat, ip, udhcpc, and ifplugd binaries or update to vendor-patched versions; follow least-privilege principles and restrict device authentication.

Recommended fix High confidence

Cc612 and Icc15xx: upgrade to firmware 5.11.2, 5.12.5, 5.13.2, or 5.20.2 (depending on your current version branch)

  1. Identify the currently installed firmware version on the Cc612 or Icc15xx Charge Controller
  2. Access the device administrative interface or use the vendor's firmware update mechanism
  3. Download the appropriate fixed firmware version based on your current version branch: 5.11.2 (if on 5.11.x), 5.12.5 (if on 5.12.x), 5.13.2 (if on 5.13.x), or 5.20.2 (if on 5.20.x)
  4. Upload and apply the firmware update following vendor documentation
  5. Verify the firmware update was successful and the device is operational
  6. Confirm the vulnerability is remediated by checking that the suid bit has been removed from socat, ip, udhcpc, and ifplugd
Caveat Firmware updates may require device downtime; verify compatibility with connected systems before 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-34591 — 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-34591 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