{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-42484 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-42484 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-42484 is a medium-severity memory corruption vulnerability in espressif esp-now, published on 12 Sep 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-42484 and fix it if it is affected.\n\nWhat it is: CVE-2024-42484 is a medium-severity memory corruption vulnerability in espressif esp-now, published on 12 Sep 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-42484 in the wild and no public exploit code.\n\nAffected product: espressif esp-now. 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-42484/ (Markdown: https://insights.sbomify.com/CVE-2024-42484/index.md)","id":"CVE-2024-42484","markdown":"https://insights.sbomify.com/CVE-2024-42484/index.md","name":"CVE-2024-42484","record":{"aliases":["GHSA-q6f6-4qc5-vhx5"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"ESP-NOW firmware","requires_auth":"none","summary":"Attackers can trigger memory corruption in ESP-NOW firmware by sending malformed group messages with invalid address counts, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"ESP-NOW Component provides a connectionless Wi-Fi communication protocol. An Out-of-Bound (OOB) vulnerability was discovered in the implementation of the ESP-NOW group type message because there is no check for the addrs_num field of the group type message. This can result in memory corruption related attacks. Normally there are two fields in the group information that need to be checked, i.e., the addrs_num field and the addrs_list fileld. Since we only checked the addrs_list field, an attacker can send a group type message with an invalid addrs_num field, which will cause the message handled by the firmware to be much larger than the current buffer, thus causing a memory corruption issue that goes beyond the payload length.","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":"ESP-NOW OOB Vulnerability In Group Type Message","id":"CVE-2024-42484","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Filament Excel Vulnerable to Path Traversal Attack on Export Download Endpoint","id":"CVE-2024-42485"},"packages":[],"prev":{"headline":"ESP-NOW Replay Attacks Vulnerability","id":"CVE-2024-42483"},"products":["esp-now"],"published":"2024-09-12","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-12","vendors":["espressif"]},"summary":"Attackers can trigger memory corruption in ESP-NOW firmware by sending malformed group messages with invalid address counts, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2024-42484/"}