{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-68473 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-68473 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68473 is a memory corruption vulnerability in espressif esp-idf, published on 26 Dec 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-68473 and fix it if it is affected.\n\nWhat it is: CVE-2025-68473 is a memory corruption vulnerability in espressif esp-idf, published on 26 Dec 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-68473 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-68473/ (Markdown: https://insights.sbomify.com/CVE-2025-68473/index.md)","id":"CVE-2025-68473","markdown":"https://insights.sbomify.com/CVE-2025-68473/index.md","name":"CVE-2025-68473","record":{"aliases":["GHSA-hmjj-rjvv-w8pq"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"ESP-IDF Bluetooth stack","requires_auth":"none","summary":"An out-of-bounds write in the ESP-IDF Bluetooth SDP handler allows attackers to potentially execute code or crash the device via crafted Bluetooth services.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"esp-idf","vendor":"espressif"}],"cvss":{"score":0,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.5.1, 5.4.3, 5.3.4, 5.2.6, 5.1.6, and earlier, in the ESP-IDF Bluetooth host stack (BlueDroid), the function bta_dm_sdp_result() used a fixed-size array uuid_list[32][MAX_UUID_SIZE] to store discovered service UUIDs during the SDP (Service Discovery Protocol) process. On modern Bluetooth devices, it is possible for the number of available services to exceed this fixed limit (32). In such cases, if more than 32 services are discovered, subsequent writes to uuid_list could exceed the bounds of the array, resulting in a potential out-of-bounds write condition.","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 Has Out-of-Bounds Read in ESP32 Bluetooth SDP Result Handling","id":"CVE-2025-68473","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"ESF-IDF Has Out-of-Bounds Write in ESP32 Bluetooth AVRCP Vendor Command Handling","id":"CVE-2025-68474"},"packages":[],"prev":{"headline":"MindsDB has improper sanitation of filepath that leads to information disclosure and DOS","id":"CVE-2025-68472"},"products":["esp-idf"],"published":"2025-12-26","related":[{"cvss_score":9.3,"headline":"ESF-IDF: Out-of-Bounds Write in ESP-TEE Secure Service Wrappers","id":"CVE-2026-45328","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2024-53406","kev_date_added":null,"published":"2025-03-13"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2021-28139","kev_date_added":null,"published":"2021-09-07"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2024-33453","kev_date_added":null,"published":"2024-10-17"},{"cvss_score":8.1,"headline":"Weak cryptography in n/a","id":"CVE-2019-12587","kev_date_added":null,"published":"2019-09-04"},{"cvss_score":7.5,"headline":"ESF-IDF: Remote Null Pointer Dereference in WebSocket Server","id":"CVE-2026-45541","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-51428","kev_date_added":null,"published":"2024-11-07"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-29","vendors":["espressif"]},"summary":"An out-of-bounds write in the ESP-IDF Bluetooth SDP handler allows attackers to potentially execute code or crash the device via crafted Bluetooth services.","url":"https://insights.sbomify.com/CVE-2025-68473/"}