{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51630 exists.","fix":"No fix has been published for CVE-2025-51630 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-51630 is a critical memory corruption vulnerability in n/a, published on 17 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-51630 and fix it if it is affected.\n\nWhat it is: CVE-2025-51630 is a critical memory corruption vulnerability in n/a, published on 17 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51630 exists.\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-51630/ (Markdown: https://insights.sbomify.com/CVE-2025-51630/index.md)","id":"CVE-2025-51630","markdown":"https://insights.sbomify.com/CVE-2025-51630/index.md","name":"CVE-2025-51630","record":{"aliases":["GHSA-hjq6-jrvq-m64c"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"TOTOLINK router","requires_auth":"none","summary":"A buffer overflow in the TOTOLINK N350RT router allows attackers to execute arbitrary code or cause a denial of service via the ePort parameter.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"n350rt_firmware","vendor":"totolink"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"TOTOLINK N350RT V9.3.5u.6139_B20201216 was discovered to contain a buffer overflow via the ePort parameter in the function setIpPortFilterRules.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2025-51630","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2025-51643"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-51629"},"products":["n/a"],"published":"2025-07-17","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2024-42966","kev_date_added":null,"published":"2024-08-15"},{"cvss_score":8.7,"headline":"TOTOLINK N350RT cstecgi.cgi setWizardCfg buffer overflow","id":"CVE-2024-7462","kev_date_added":null,"published":"2024-08-05"},{"cvss_score":8.7,"headline":"TOTOLINK N350RT cstecgi.cgi setParentalRules buffer overflow","id":"CVE-2024-7333","kev_date_added":null,"published":"2024-08-01"},{"cvss_score":7.8,"headline":"Command injection in n/a","id":"CVE-2022-36479","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2022-36480","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":7.8,"headline":"Command injection in n/a","id":"CVE-2022-36481","kev_date_added":null,"published":"2022-08-25"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-07-17","vendors":["n/a"]},"summary":"A buffer overflow in the TOTOLINK N350RT router allows attackers to execute arbitrary code or cause a denial of service via the ePort parameter.","url":"https://insights.sbomify.com/CVE-2025-51630/"}