{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36178 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36178 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36178 is a critical command injection vulnerability in n/a, published on 6 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-36178 and fix it if it is affected.\n\nWhat it is: CVE-2020-36178 is a critical command injection vulnerability in n/a, published on 6 Jan 2021. 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-2020-36178 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-2020-36178/ (Markdown: https://insights.sbomify.com/CVE-2020-36178/index.md)","id":"CVE-2020-36178","markdown":"https://insights.sbomify.com/CVE-2020-36178/index.md","name":"CVE-2020-36178","record":{"aliases":["GHSA-qqg6-4j54-68gr"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"TP-Link router","requires_auth":"none","summary":"Attackers can execute arbitrary OS commands on TP-Link TL-WR840N routers via IP address fields in the web interface due to unsafe system calls.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tl-wr840n_firmware","vendor":"tp-link"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"oal_ipt_addBridgeIsolationRules on TP-Link TL-WR840N 6_EU_0.9.1_4.16 devices allows OS command injection because a raw string entered from the web interface (an IP address field) is used directly for a call to the system library function (for iptables). NOTE: oal_ipt_addBridgeIsolationRules is not the only function that calls util_execSystem.","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-2020-36178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Unsafe Deserialization in jackson-databind","id":"CVE-2020-36179"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-36177"},"products":["n/a"],"published":"2021-01-06","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-25060","kev_date_added":null,"published":"2022-02-25"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-25061","kev_date_added":null,"published":"2022-02-25"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-25064","kev_date_added":null,"published":"2022-02-25"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2021-41653","kev_date_added":null,"published":"2021-11-13"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2018-11714","kev_date_added":null,"published":"2018-06-04"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2019-15060","kev_date_added":null,"published":"2019-08-22"}],"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-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary OS commands on TP-Link TL-WR840N routers via IP address fields in the web interface due to unsafe system calls.","url":"https://insights.sbomify.com/CVE-2020-36178/"}