{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-0650 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-0650 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-0650 is a medium-severity memory corruption vulnerability in TP-Link TL-WR940N, published on 28 Mar 2023. 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-0650 and fix it if it is affected.\n\nWhat it is: CVE-2022-0650 is a medium-severity memory corruption vulnerability in TP-Link TL-WR940N, published on 28 Mar 2023. 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-0650 in the wild and no public exploit code.\n\nAffected product: TP-Link TL-WR940N. 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-0650/ (Markdown: https://insights.sbomify.com/CVE-2022-0650/index.md)","id":"CVE-2022-0650","markdown":"https://insights.sbomify.com/CVE-2022-0650/index.md","name":"CVE-2022-0650","record":{"aliases":["GHSA-c55h-3vqx-vr2v"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link router","requires_auth":"high_privilege","summary":"Authenticated network-adjacent attackers can execute arbitrary code as root on TP-Link routers via a stack-based buffer overflow in the httpd service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"tl-wr940n_firmware","vendor":"tp-link"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of TP-Link TL-WR940N 3.20.1 Build 200316 Rel.34392n (5553) routers. Authentication is required to exploit this vulnerability. The specific flaw exists within the httpd service, which listens on TCP port 80 by default. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-13993.","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":"Memory corruption in TL-WR940N","id":"CVE-2022-0650","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"WP Statistics \u003c= 13.1.5 Unauthenticated Blind SQL Injection via current_page_type","id":"CVE-2022-0651"},"packages":[],"prev":{"headline":"Adrotate \u003c 5.8.23 - Admin+ XSS via Group Name","id":"CVE-2022-0649"},"products":["TL-WR940N"],"published":"2023-03-28","related":[{"cvss_score":9.9,"headline":"Memory corruption in n/a","id":"CVE-2023-36355","kev_date_added":null,"published":"2023-06-22"},{"cvss_score":8.8,"headline":"Memory corruption in TL-WR940N","id":"CVE-2022-24355","kev_date_added":null,"published":"2022-02-18"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2019-6989","kev_date_added":null,"published":"2019-06-06"},{"cvss_score":8.5,"headline":"OS Command Injection in IPv6 PPPoE Configuration in TP-Link TL-WR940N","id":"CVE-2026-11409","kev_date_added":null,"published":"2026-06-16"},{"cvss_score":8.5,"headline":"OS Command Injection in BigPond Cable (BPA) Configuration in TP-Link TL-WR940N","id":"CVE-2026-11410","kev_date_added":null,"published":"2026-06-16"},{"cvss_score":8.2,"headline":"TP-Link TL-WR940N, TL-WR841N WanSlaacCfgRpm.htm buffer overflow","id":"CVE-2025-6151","kev_date_added":null,"published":"2025-06-17"},{"cvss_score":8,"headline":"Memory corruption in n/a","id":"CVE-2024-54887","kev_date_added":null,"published":"2025-01-09"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-19","vendors":["TP-Link"]},"summary":"Authenticated network-adjacent attackers can execute arbitrary code as root on TP-Link routers via a stack-based buffer overflow in the httpd service.","url":"https://insights.sbomify.com/CVE-2022-0650/"}