{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-49604 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-49604 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-49604 is a medium-severity memory corruption vulnerability in n/a, published on 9 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-49604 and fix it if it is affected.\n\nWhat it is: CVE-2025-49604 is a medium-severity memory corruption vulnerability in n/a, published on 9 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-49604 in the wild and no public exploit code.\n\nAffected product: n/a. 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-49604/ (Markdown: https://insights.sbomify.com/CVE-2025-49604/index.md)","id":"CVE-2025-49604","markdown":"https://insights.sbomify.com/CVE-2025-49604/index.md","name":"CVE-2025-49604","record":{"aliases":["GHSA-c4jh-w3h2-9h7c"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Realtek AmebaD IoT","requires_auth":"low_privilege","summary":"Heap-based buffer overflow in Realtek AmebaD WLAN driver allows attackers to execute code or cause denial of service via fragmented Wi-Fi frames.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"For Realtek AmebaD devices, a heap-based buffer overflow was discovered in Ameba-AIoT ameba-arduino-d before version 3.1.9 and ameba-rtos-d before commit c2bfd8216a1cbc19ad2ab5f48f372ecea756d67a on 2025/07/03. In the WLAN driver defragment function, lack of validation of the size of fragmented Wi-Fi frames may lead to a heap-based buffer overflow.","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":"Memory corruption in n/a","id":"CVE-2025-49604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in Obsidian","id":"CVE-2025-49618"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-49603"},"products":["n/a"],"published":"2025-07-09","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-09-22","vendors":["n/a"]},"summary":"Heap-based buffer overflow in Realtek AmebaD WLAN driver allows attackers to execute code or cause denial of service via fragmented Wi-Fi frames.","url":"https://insights.sbomify.com/CVE-2025-49604/"}