{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-53845 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-53845 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-53845 is a medium-severity vulnerability in espressif esp-idf, published on 11 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-53845 and fix it if it is affected.\n\nWhat it is: CVE-2024-53845 is a medium-severity vulnerability in espressif esp-idf, published on 11 Dec 2024. 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-2024-53845 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-2024-53845/ (Markdown: https://insights.sbomify.com/CVE-2024-53845/index.md)","id":"CVE-2024-53845","markdown":"https://insights.sbomify.com/CVE-2024-53845/index.md","name":"CVE-2024-53845","record":{"aliases":["GHSA-wm57-466g-mhrr"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ESP-IDF IoT framework","requires_auth":"none","summary":"Attackers can decrypt ESPTouch v2 provisioning data due to a constant zero IV, exposing sensitive IoT configuration information.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-909","name":"Missing Initialization of Resource"},{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"ESPTouch is a connection protocol for internet of things devices. In the ESPTouchV2 protocol, while there is an option to use a custom AES key, there is no option to set the IV (Initialization Vector) prior to versions 5.3.2, 5.2.4, 5.1.6, and 5.0.8. The IV is set to zero and remains constant throughout the product's lifetime. In AES/CBC mode, if the IV is not properly initialized, the encrypted output becomes deterministic, leading to potential data leakage. To address the aforementioned issues, the application generates a random IV when activating the AES key starting in versions 5.3.2, 5.2.4, 5.1.6, and 5.0.8. This IV is then transmitted along with the provision data to the provision device. The provision device has also been equipped with a parser for the AES IV. The upgrade is applicable for all applications and users of ESPTouch v2 component from ESP-IDF. As it is implemented in the ESP Wi-Fi 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":"AES/CBC Constant IV Vulnerability in ESPTouch v2","id":"CVE-2024-53845","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":0,"n_references":9,"next":{"headline":"ssl fails to validate incorrect extened key usage","id":"CVE-2024-53846"},"packages":[],"prev":{"headline":"Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in labsai/eddi","id":"CVE-2024-53844"},"products":["esp-idf"],"published":"2024-12-11","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":"2024-12-12","vendors":["espressif"]},"summary":"Attackers can decrypt ESPTouch v2 provisioning data due to a constant zero IV, exposing sensitive IoT configuration information.","url":"https://insights.sbomify.com/CVE-2024-53845/"}