Security readout for executives and security teams
Plain-English summary
This flaw affects Bender/ebee EV charge controllers. A specially long URL sent to the device webserver can crash that webserver, disrupting management or service availability. The public record describes limited availability impact, not data theft or device takeover.
Executive priority
Treat this as a moderate operational resilience issue for EV charging infrastructure. Prioritize exposed or business-critical controllers first, especially where web access crosses untrusted networks. It is not documented as actively exploited in the supplied sources.
Technical view
CVE-2021-34587 is a network-reachable stack buffer issue in affected CC612, CC613, ICC15xx, and ICC16xx firmware branches. The URL is used as input to sprintf into a stack variable, and excessive length can crash the webserver. CVSS 3.1 is 5.3: unauthenticated, low complexity, availability-only impact.
Likely exposure
Exposure is most likely where affected charge controllers expose their web interface to operators, building networks, charger management networks, or the internet. Products listed are CC612, CC613, ICC15xx, and ICC16xx running 5.11.x, 5.12.x, 5.13.x, or 5.20.x.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. The vulnerability is remotely reachable and unauthenticated, but the documented outcome is webserver crash with low availability impact. No exploit steps or public weaponization details are provided in the supplied sources.
Researcher notes
Evidence supports CWE-121-style stack overwrite risk, but the public description only confirms webserver crash. Do not assume code execution, broader charger control impact, or a specific patch version without vendor advisory confirmation.
Mitigation direction
- Identify affected Bender/ebee controller models and firmware branches.
- Check Bender or VDE guidance for fixed firmware or vendor-approved workarounds.
- Restrict webserver access to trusted administration networks only.
- Avoid exposing charge controller web interfaces directly to the internet.
- Monitor affected devices for unexpected webserver restarts or management outages.
Validation and detection
- Inventory CC612, CC613, ICC15xx, and ICC16xx deployments.
- Confirm whether firmware is in 5.11.x, 5.12.x, 5.13.x, or 5.20.x.
- Review network paths to each controller web interface.
- Check operational logs for unexplained webserver crashes or restarts.
- Verify remediation status against Bender or VDE advisory information.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-34587 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://cert.vde.com/en/advisories/VDE-2021-047CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.