{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36460 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36460 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36460 is a high-severity command injection vulnerability in n/a, published on 25 Aug 2022. 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-2022-36460 and fix it if it is affected.\n\nWhat it is: CVE-2022-36460 is a high-severity command injection vulnerability in n/a, published on 25 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36460 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-2022-36460/ (Markdown: https://insights.sbomify.com/CVE-2022-36460/index.md)","id":"CVE-2022-36460","markdown":"https://insights.sbomify.com/CVE-2022-36460/index.md","name":"CVE-2022-36460","record":{"aliases":["GHSA-qqhv-2h68-rx7f"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TOTOLINK router","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands on TOTOLINK A3700R routers via the FileName parameter in the firmware upload function.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"a3700r_firmware","vendor":"totolink"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"TOTOLINK A3700R V9.1.2u.6134_B20201202 was discovered to contain a command injection vulnerability via the FileName parameter in the function UploadFirmwareFile.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2022-36460","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2022-36461"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2022-36459"},"products":["n/a"],"published":"2022-08-25","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-42545","kev_date_added":null,"published":"2024-08-12"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-37637","kev_date_added":null,"published":"2024-06-14"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-37634","kev_date_added":null,"published":"2024-06-13"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-37635","kev_date_added":null,"published":"2024-06-13"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-22660","kev_date_added":null,"published":"2024-01-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-22662","kev_date_added":null,"published":"2024-01-23"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2024-22663","kev_date_added":null,"published":"2024-01-23"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands on TOTOLINK A3700R routers via the FileName parameter in the firmware upload function.","url":"https://insights.sbomify.com/CVE-2022-36460/"}