{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-46912 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-46912 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-46912 is a high-severity vulnerability in n/a, published on 20 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-46912 and fix it if it is affected.\n\nWhat it is: CVE-2022-46912 is a high-severity vulnerability in n/a, published on 20 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-46912 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-46912/ (Markdown: https://insights.sbomify.com/CVE-2022-46912/index.md)","id":"CVE-2022-46912","markdown":"https://insights.sbomify.com/CVE-2022-46912/index.md","name":"CVE-2022-46912","record":{"aliases":["GHSA-4q79-fg6h-v56p"],"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":"TP-Link router firmware","requires_auth":"none","summary":"Attackers can execute arbitrary code or cause denial of service on TP-Link routers by uploading a crafted firmware image during the update process.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tl-wr841n_firmware","vendor":"tp-link"},{"product":"tl-wr841nd_v7_firmware","vendor":"tp-link"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue in the firmware update process of TP-Link TL-WR841N / TL-WA841ND V7 3.13.9 and earlier allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via uploading a crafted firmware image.","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":"File upload in n/a","id":"CVE-2022-46912","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2022-46914"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2022-46910"},"products":["n/a"],"published":"2022-12-20","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-25073","kev_date_added":null,"published":"2022-02-22"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2018-12575","kev_date_added":null,"published":"2018-07-02"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2020-35576","kev_date_added":null,"published":"2021-01-25"},{"cvss_score":8.8,"headline":"Memory corruption in TL-WR841N","id":"CVE-2019-17147","kev_date_added":null,"published":"2020-01-07"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-12574","kev_date_added":null,"published":"2018-07-02"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2018-12577","kev_date_added":null,"published":"2018-07-02"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-16","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code or cause denial of service on TP-Link routers by uploading a crafted firmware image during the update process.","url":"https://insights.sbomify.com/CVE-2022-46912/"}