{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2021-34589 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-34589 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-34589 is a high-severity vulnerability in Bender / ebee CC612, published on 27 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-34589 and fix it if it is affected.\n\nWhat it is: CVE-2021-34589 is a high-severity vulnerability in Bender / ebee CC612, published on 27 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-34589 in the wild and no public exploit code.\n\nAffected product: Bender / ebee CC612. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-34589/ (Markdown: https://insights.sbomify.com/CVE-2021-34589/index.md)","id":"CVE-2021-34589","markdown":"https://insights.sbomify.com/CVE-2021-34589/index.md","name":"CVE-2021-34589","record":{"aliases":["GHSA-c36w-9wvv-9rh6"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"EV charge controller","requires_auth":"none","summary":"Attackers can read the RFID of the last charge event without authentication via the web interface of Bender ebee charge controllers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERTVDE","cpe":[{"product":"cc612_firmware","vendor":"bender"},{"product":"cc613_firmware","vendor":"bender"},{"product":"icc15xx_firmware","vendor":"bender"},{"product":"icc16xx_firmware","vendor":"bender"},{"product":"icc613_firmware","vendor":"bender"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Bender Charge Controller: RFID leak","id":"CVE-2021-34589","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Bender Charge Controller: Cross-site Scripting","id":"CVE-2021-34590"},"packages":[],"prev":{"headline":"Bender Charge Controller: Unprotected data export","id":"CVE-2021-34588"},"products":["CC612","CC613","ICC15xx","ICC16xx"],"published":"2022-04-27","related":[{"cvss_score":9.8,"headline":"Bender Charge Controller: Hardcoded Credentials in Charge Controller","id":"CVE-2021-34601","kev_date_added":null,"published":"2022-04-27"},{"cvss_score":8.8,"headline":"Bender Charge Controller: Command injection via Web interface","id":"CVE-2021-34592","kev_date_added":null,"published":"2022-04-27"},{"cvss_score":8.8,"headline":"Bender Charge Controller: Long URL could lead to webserver crash","id":"CVE-2021-34602","kev_date_added":null,"published":"2022-04-27"},{"cvss_score":8.6,"headline":"Bender Charge Controller: Unprotected data export","id":"CVE-2021-34588","kev_date_added":null,"published":"2022-04-27"},{"cvss_score":7.8,"headline":"Bender Charge Controller: Local privilege Escalation","id":"CVE-2021-34591","kev_date_added":null,"published":"2022-04-27"},{"cvss_score":5.4,"headline":"Bender Charge Controller: Cross-site Scripting","id":"CVE-2021-34590","kev_date_added":null,"published":"2022-04-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Bender / ebee"]},"summary":"Attackers can read the RFID of the last charge event without authentication via the web interface of Bender ebee charge controllers.","url":"https://insights.sbomify.com/CVE-2021-34589/"}