{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-16340 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16340 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16340 is a critical vulnerability in n/a, published on 21 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-16340 and fix it if it is affected.\n\nWhat it is: CVE-2019-16340 is a critical vulnerability in n/a, published on 21 Nov 2019. 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-2019-16340 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-2019-16340/ (Markdown: https://insights.sbomify.com/CVE-2019-16340/index.md)","id":"CVE-2019-16340","markdown":"https://insights.sbomify.com/CVE-2019-16340/index.md","name":"CVE-2019-16340","record":{"aliases":["GHSA-7rqp-qm5j-jm9c"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Linksys Velop router","requires_auth":"none","summary":"Remote attackers can obtain the recovery key by accessing a specific URI on Linksys Velop devices, potentially compromising device security.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"velop_whw0301_firmware","vendor":"linksys"},{"product":"velop_whw0302_firmware","vendor":"linksys"},{"product":"velop_whw0303_firmware","vendor":"linksys"}],"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-425","name":"Direct Request"}],"description":"Belkin Linksys Velop 1.1.8.192419 devices allows remote attackers to discover the recovery key via a direct request for the /sysinfo_json.cgi URI.","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":"Information disclosure in n/a","id":"CVE-2019-16340","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-16344"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2019-16338"},"products":["n/a"],"published":"2019-11-21","related":[],"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-05","vendors":["n/a"]},"summary":"Remote attackers can obtain the recovery key by accessing a specific URI on Linksys Velop devices, potentially compromising device security.","url":"https://insights.sbomify.com/CVE-2019-16340/"}