{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41540 exists.","fix":"No fix has been published for CVE-2022-41540 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41540 is a medium-severity vulnerability in n/a, published on 18 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-41540 and fix it if it is affected.\n\nWhat it is: CVE-2022-41540 is a medium-severity vulnerability in n/a, published on 18 Oct 2022. 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-2022-41540 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-2022-41540/ (Markdown: https://insights.sbomify.com/CVE-2022-41540/index.md)","id":"CVE-2022-41540","markdown":"https://insights.sbomify.com/CVE-2022-41540/index.md","name":"CVE-2022-41540","record":{"aliases":["GHSA-x34h-6cf7-qmw4"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TP-Link router","requires_auth":"none","summary":"Attackers can intercept communications and brute-force hard-coded keys to access sensitive information on TP-Link AX10v1 routers.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ax10_firmware","vendor":"tp-link"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"The web app client of TP-Link AX10v1 V1_211117 uses hard-coded cryptographic keys when communicating with the router. Attackers who are able to intercept the communications between the web client and router through a man-in-the-middle attack can then obtain the sequence key via a brute-force attack, and access sensitive information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-05-27","github_poc":1,"max_poc_stars":16,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-05-27T21:09:03Z","kind":"github_poc","ref":"https://github.com/efchatz/easy-exploits","stars":16,"title":"Exploits of different CVE IDs (CVE-2021-37910, CVE-2021-40288, CVE-2021-41435, CVE-2021-41436, CVE-2021-41437, CVE-2021-41441, CVE-2021-41442, CVE-2021-41445, CVE-2021-41449, CVE-2021-41450, CVE-2021-41451, CVE-2021-41753, CVE-2021-41788, CVE-2021-46353, CVE-2022-41540, CVE-2022-41541)"}],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41540","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2022-41541"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2022-41539"},"products":["n/a"],"published":"2022-10-18","related":[{"cvss_score":8.1,"headline":"Auth bypass in n/a","id":"CVE-2022-41541","kev_date_added":null,"published":"2022-10-18"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-15","vendors":["n/a"]},"summary":"Attackers can intercept communications and brute-force hard-coded keys to access sensitive information on TP-Link AX10v1 routers.","url":"https://insights.sbomify.com/CVE-2022-41540/"}