CVE-2021-34589: Bender Charge Controller: RFID leak
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.99% (FIRST EPSS); higher than 62.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In Bender/ebee Charge Controllers in multiple versions are prone to an RFID leak. The RFID of the last charge event can be read without authentication via the web interface.
- Published
- Apr 27, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.9% · 62th percentile
- CWE
- CWE-200
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CNA vs NVD score
- NVD
- 7.5
- CNA · CERTVDE
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| bender | cc612 firmware | cpe:2.3:o:bender:cc612_firmware |
| bender | cc612 | cpe:2.3:h:bender:cc612 |
| bender | cc613 firmware | cpe:2.3:o:bender:cc613_firmware |
| bender | icc613 firmware | cpe:2.3:o:bender:icc613_firmware |
| bender | cc613 | cpe:2.3:h:bender:cc613 |
| bender | icc15xx firmware | cpe:2.3:o:bender:icc15xx_firmware |
| bender | icc15xx | cpe:2.3:h:bender:icc15xx |
| bender | icc16xx firmware | cpe:2.3:o:bender:icc16xx_firmware |
| bender | icc16xx | cpe:2.3:h:bender:icc16xx |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- bender cc612 firmware5.11.0 and later · before 5.11.2
- bender cc612 firmware5.12.0 and later · before 5.12.5
- bender cc612 firmware5.13.0 and later · before 5.13.2
- bender cc612 firmware5.20.0 and later · before 5.20.2
- bender cc613 firmware5.11.0 and later · before 5.11.2
- bender cc613 firmware5.13.0 and later · before 5.13.2
- bender cc613 firmware5.20.0 and later · before 5.20.2
- bender icc15xx firmware5.11.0 and later · before 5.11.2
- bender icc15xx firmware5.12.0 and later · before 5.12.5
- bender icc15xx firmware5.13.0 and later · before 5.13.2
- bender icc15xx firmware5.20.0 and later · before 5.20.2
- bender icc16xx firmware5.20.0 and later · before 5.20.2
- bender icc16xx firmware5.11.0 and later · before 5.11.2
- bender icc16xx firmware5.12.0 and later · before 5.12.5
- bender icc16xx firmware5.13.0 and later · before 5.13.2
- bender icc613 firmware5.12.0 and later · before 5.12.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
Bender / ebee CC612
- 5.11.x and later · before 5.11.2affected
- 5.12.x and later · before 5.12.5affected
- 5.13.x and later · before 5.13.2affected
- 5.20.x and later · before 5.20.2affected
Bender / ebee CC613
- 5.11.x and later · before 5.11.2affected
- 5.12.x and later · before 5.12.5affected
- 5.13.x and later · before 5.13.2affected
- 5.20.x and later · before 5.20.2affected
Bender / ebee ICC15xx
- 5.11.x and later · before 5.11.2affected
- 5.12.x and later · before 5.12.5affected
- 5.13.x and later · before 5.13.2affected
- 5.20.x and later · before 5.20.2affected
Bender / ebee ICC16xx
- 5.11.x and later · before 5.11.2affected
- 5.12.x and later · before 5.12.5affected
- 5.13.x and later · before 5.13.2affected
- 5.20.x and later · before 5.20.2affected
Same product
bender: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-34601Bender Charge Controller: Hardcoded Credentials in Charge Controller39Monitor
- CVE-2021-34602Bender Charge Controller: Long URL could lead to webserver crash35Monitor
- CVE-2021-34592Bender Charge Controller: Command injection via Web interface35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-34587Apr 27, 2022 · Bender Charge Controller: Long URL could lead to webserver crash21Monitor
- ← EarlierCVE-2021-34588Apr 27, 2022 · Bender Charge Controller: Unprotected data export34Monitor
- Later →CVE-2021-34590Apr 27, 2022 · Bender Charge Controller: Cross-site Scripting21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- the IT security researchersOpenSource Security GmbH for their thorough and in-depth work. The issue was coordinated by CERT@VDE.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
—
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2021-345920 days apartBender Charge Controller: Command injection via Web interface35Monitor
- CVE-2021-346020 days apartBender Charge Controller: Long URL could lead to webserver crash35Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-200 · Exposure of Sensitive Information to an Unauthorized ActorCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.
The bug in code
The whole CWE-200 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
{
"permissions": ["tabs", "<all_urls>"],
"background": { "service_worker": "analytics.js" }
}Fixed
{
"permissions": ["activeTab"],
"host_permissions": ["https://yildiz.example/*"]
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- ExcavationCAPEC-116likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- FootprintingCAPEC-169likelihood: High · Very Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- FingerprintingCAPEC-224likelihood: High · Very Low
- ICMP Echo Request PingCAPEC-285likelihood: Medium · Low
- TCP SYN ScanCAPEC-287Low
- Enumerate Mail Exchange (MX) RecordsCAPEC-290Low
ATT&CK techniques
- System Service DiscoveryT1007
- System Network Configuration DiscoveryT1016
- Remote System DiscoveryT1018
- System Owner/User DiscoveryT1033
- Masquerading: Match Legitimate Name or LocationT1036.005
- Network Service ScanningT1046
- System Network Connections DiscoveryT1049
- Process DiscoveryT1057
- Permission Groups DiscoveryT1069
- System Information DiscoveryT1082
- File and Directory DiscoveryT1083
- Account DiscoveryT1087
- Multi-Factor Authentication InterceptionT1111
- Peripheral Device DiscoveryT1120
- System Time DiscoveryT1124
- Access Token Manipulation:Token Impersonation/TheftT1134.001
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.