{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34450 exists.","fix":"Apply the vendor's patch.","what":"CVE-2025-34450 is a medium-severity memory corruption vulnerability in merbanan rtl_433, published on 18 Dec 2025. 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-2025-34450 and fix it if it is affected.\n\nWhat it is: CVE-2025-34450 is a medium-severity memory corruption vulnerability in merbanan rtl_433, published on 18 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34450 exists.\n\nAffected product: merbanan rtl_433. 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-34450/ (Markdown: https://insights.sbomify.com/CVE-2025-34450/index.md)","id":"CVE-2025-34450","markdown":"https://insights.sbomify.com/CVE-2025-34450/index.md","name":"CVE-2025-34450","record":{"aliases":["DEBIAN-CVE-2025-34450","GHSA-h7qg-49w9-4cpx","UBUNTU-CVE-2025-34450"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RTL-SDR software","requires_auth":"none","summary":"Attackers can cause memory corruption and potential code execution in rtl_433 by providing crafted raw RF input data.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"rtl_433","vendor":"rtl_433_project"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"merbanan/rtl_433 versions up to and including 25.02 and prior to commit 25e47f8 contain a stack-based buffer overflow vulnerability in the function parse_rfraw() located in src/rfraw.c. When processing crafted or excessively large raw RF input data, the application may write beyond the bounds of a stack buffer, resulting in memory corruption or a crash. This vulnerability can be exploited to cause a denial of service and, under certain conditions, may be leveraged for further exploitation depending on the execution environment and available mitigations.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"merbanan/rtl_433 \u003c= 25.02 Stack-based Buffer Overflow","id":"CVE-2025-34450","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"rofl0r/proxychains-ng \u003c= 4.17 Stack-based Buffer Overflow","id":"CVE-2025-34451"},"packages":[],"prev":{"headline":"Genymobile/scrcpy \u003c= 3.3.3 Global Buffer Overflow","id":"CVE-2025-34449"},"products":["rtl_433"],"published":"2025-12-18","related":[{"cvss_score":5.5,"headline":"Memory corruption in n/a","id":"CVE-2022-27419","kev_date_added":null,"published":"2022-04-12"},{"cvss_score":5.5,"headline":"Integer overflow in n/a","id":"CVE-2022-25051","kev_date_added":null,"published":"2022-03-01"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["merbanan"]},"summary":"Attackers can cause memory corruption and potential code execution in rtl_433 by providing crafted raw RF input data.","url":"https://insights.sbomify.com/CVE-2025-34450/"}