{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-64342 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-64342 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-64342 is a medium-severity denial of service vulnerability in espressif esp-idf, published on 17 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-64342 and fix it if it is affected.\n\nWhat it is: CVE-2025-64342 is a medium-severity denial of service vulnerability in espressif esp-idf, published on 17 Nov 2025. 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-2025-64342 in the wild and no public exploit code.\n\nAffected product: espressif esp-idf. 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-64342/ (Markdown: https://insights.sbomify.com/CVE-2025-64342/index.md)","id":"CVE-2025-64342","markdown":"https://insights.sbomify.com/CVE-2025-64342/index.md","name":"CVE-2025-64342","record":{"aliases":["GHSA-8mg7-9qpg-p92v"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"ESP32 IoT framework","requires_auth":"none","summary":"An attacker can cause unexpected advertising stop and false connection reports in ESP32 devices by sending invalid Bluetooth access addresses.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. When the ESP32 is in advertising mode, if it receives a connection request containing an invalid Access Address (AA) of 0x00000000 or 0xFFFFFFFF, advertising may stop unexpectedly. In this case, the controller may incorrectly report a connection event to the host, which can cause the application layer to assume that the device has successfully established a connection. This issue has been fixed in versions 5.5.2, 5.4.3, 5.3.5, 5.2.6, and 5.1.7. At time of publication versions 5.5.2, 5.3.5, and 5.1.7 have not been released but are fixed respectively in commits 3b95b50, e3d7042, and 75967b5.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"ESF-IDF's ESP32 Bluetooth Controller Has an Invalid Access Address Vulnerability","id":"CVE-2025-64342","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"(conda) Constructor: Excessive permissions during and after installation","id":"CVE-2025-64343"},"packages":[],"prev":{"headline":"FastMCP has a Command Injection vulnerability - Gemini CLI","id":"CVE-2025-64340"},"products":["esp-idf"],"published":"2025-11-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-11-17","vendors":["espressif"]},"summary":"An attacker can cause unexpected advertising stop and false connection reports in ESP32 devices by sending invalid Bluetooth access addresses.","url":"https://insights.sbomify.com/CVE-2025-64342/"}