{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24893 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-24893 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-24893 is a high-severity memory corruption vulnerability in espressif esp-idf, published on 25 Jun 2022. 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-2022-24893 and fix it if it is affected.\n\nWhat it is: CVE-2022-24893 is a high-severity memory corruption vulnerability in espressif esp-idf, published on 25 Jun 2022. 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-2022-24893 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-2022-24893/ (Markdown: https://insights.sbomify.com/CVE-2022-24893/index.md)","id":"CVE-2022-24893","markdown":"https://insights.sbomify.com/CVE-2022-24893/index.md","name":"CVE-2022-24893","record":{"aliases":["GHSA-7f7f-jj2q-28wm"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Espressif Bluetooth Mesh","requires_auth":"none","summary":"Attackers can trigger memory corruption during Bluetooth Mesh provisioning to gain full system control, requiring firmware upgrades.","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":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-788","name":"Access of Memory Location After End of Buffer"},{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"ESP-IDF is the official development framework for Espressif SoCs. In Espressif’s Bluetooth Mesh SDK (`ESP-BLE-MESH`), a memory corruption vulnerability can be triggered during provisioning, because there is no check for the `SegN` field of the Transaction Start PDU. This can result in memory corruption related attacks and potentially attacker gaining control of the entire system. Patch commits are available on the 4.1, 4.2, 4.3 and 4.4 branches and users are recommended to upgrade. The upgrade is applicable for all applications and users of `ESP-BLE-MESH` component from `ESP-IDF`. As it is implemented in the Bluetooth Mesh stack, there is no workaround for the user to fix the application layer without upgrading the underlying firmware.","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":"Espressif Bluetooth Mesh Stack Vulnerable to Out-of-bounds Write leading to memory buffer corruption","id":"CVE-2022-24893","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Symfony storing cookie headers in HttpCache","id":"CVE-2022-24894"},"packages":[],"prev":{"headline":"Multiple valid tokens for password reset in Shopware","id":"CVE-2022-24892"},"products":["esp-idf"],"published":"2022-06-25","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["espressif"]},"summary":"Attackers can trigger memory corruption during Bluetooth Mesh provisioning to gain full system control, requiring firmware upgrades.","url":"https://insights.sbomify.com/CVE-2022-24893/"}