{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-5750 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-5750 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5750 is a high-severity memory corruption vulnerability in WOLFBOX Level 2 EV Charger, published on 6 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-5750 and fix it if it is affected.\n\nWhat it is: CVE-2025-5750 is a high-severity memory corruption vulnerability in WOLFBOX Level 2 EV Charger, published on 6 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-5750 in the wild and no public exploit code.\n\nAffected product: WOLFBOX Level 2 EV Charger. 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-2025-5750/ (Markdown: https://insights.sbomify.com/CVE-2025-5750/index.md)","id":"CVE-2025-5750","markdown":"https://insights.sbomify.com/CVE-2025-5750/index.md","name":"CVE-2025-5750","record":{"aliases":["GHSA-4j3x-r4j7-3jvg"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charger","requires_auth":"none","summary":"Network-adjacent attackers can execute arbitrary code on WOLFBOX Level 2 EV Chargers via a heap-based buffer overflow in the activation result parser.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"level_2_ev_charger_firmware","vendor":"wolfbox"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"WOLFBOX Level 2 EV Charger tuya_svc_devos_activate_result_parse Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of WOLFBOX Level 2 EV Charger. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the handling of the secKey, localKey, stdTimeZone and devId parameters. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-26294.","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":"Memory corruption in Level 2 EV Charger","id":"CVE-2025-5750","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WOLFBOX Level 2 EV Charger Management Card Hard-coded Credentials Authentication Bypass Vulnerability","id":"CVE-2025-5751"},"packages":[],"prev":{"headline":"WOLFBOX Level 2 EV Charger BLE Encryption Keys Uninitialized Variable Authentication Bypass Vulnerability","id":"CVE-2025-5749"},"products":["Level 2 EV Charger"],"published":"2025-06-06","related":[{"cvss_score":8,"headline":"WOLFBOX Level 2 EV Charger MCU Command Parsing Misinterpretation of Input Remote Code Execution Vulnerability","id":"CVE-2025-5747","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":8,"headline":"WOLFBOX Level 2 EV Charger LAN OTA Exposed Dangerous Method Remote Code Execution Vulnerability","id":"CVE-2025-5748","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":6.3,"headline":"WOLFBOX Level 2 EV Charger BLE Encryption Keys Uninitialized Variable Authentication Bypass Vulnerability","id":"CVE-2025-5749","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":4.6,"headline":"WOLFBOX Level 2 EV Charger Management Card Hard-coded Credentials Authentication Bypass Vulnerability","id":"CVE-2025-5751","kev_date_added":null,"published":"2025-06-06"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-06","vendors":["WOLFBOX"]},"summary":"Network-adjacent attackers can execute arbitrary code on WOLFBOX Level 2 EV Chargers via a heap-based buffer overflow in the activation result parser.","url":"https://insights.sbomify.com/CVE-2025-5750/"}