{"answers":{"affected":"It affects 20 products.","exploited":"There is no known exploitation of CVE-2014-8244 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-8244 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-8244 is a high-severity vulnerability in n/a, published on 1 Nov 2014. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-8244 and fix it if it is affected.\n\nWhat it is: CVE-2014-8244 is a high-severity vulnerability in n/a, published on 1 Nov 2014. 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-2014-8244 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-2014-8244/ (Markdown: https://insights.sbomify.com/CVE-2014-8244/index.md)","id":"CVE-2014-8244","markdown":"https://insights.sbomify.com/CVE-2014-8244/index.md","name":"CVE-2014-8244","record":{"aliases":["GHSA-w67x-x69g-q4hv"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Linksys SMART WiFi router","requires_auth":"none","summary":"Remote attackers can obtain sensitive information or modify data on Linksys SMART WiFi routers via a JNAP action in an HTTP request.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"e4200v2","vendor":"linksys"},{"product":"e4200v2_firmware","vendor":"linksys"},{"product":"ea2700","vendor":"linksys"},{"product":"ea2700_firmware","vendor":"linksys"},{"product":"ea3500","vendor":"linksys"},{"product":"ea3500_firmware","vendor":"linksys"},{"product":"ea4500","vendor":"linksys"},{"product":"ea4500_firmware","vendor":"linksys"},{"product":"ea6200","vendor":"linksys"},{"product":"ea6200_firmware","vendor":"linksys"},{"product":"ea6300","vendor":"linksys"},{"product":"ea6300_firmware","vendor":"linksys"},{"product":"ea6400","vendor":"linksys"},{"product":"ea6400_firmware","vendor":"linksys"},{"product":"ea6500","vendor":"linksys"},{"product":"ea6500_firmware","vendor":"linksys"},{"product":"ea6700","vendor":"linksys"},{"product":"ea6700_firmware","vendor":"linksys"},{"product":"ea6900","vendor":"linksys"},{"product":"ea6900_firmware","vendor":"linksys"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Linksys SMART WiFi firmware on EA2700 and EA3500 devices; before 2.1.41 build 162351 on E4200v2 and EA4500 devices; before 1.1.41 build 162599 on EA6200 devices; before 1.1.40 build 160989 on EA6300, EA6400, EA6500, and EA6700 devices; and before 1.1.42 build 161129 on EA6900 devices allows remote attackers to obtain sensitive information or modify data via a JNAP action in a JNAP/ HTTP request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-01-24","github_poc":1,"max_poc_stars":6,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-01-24T19:14:49Z","kind":"github_poc","ref":"https://github.com/JollyJumbuckk/LinksysLeaks","stars":6,"title":"Python3 script to scan for Linksys smart wifi devices that are vulnerable to CVE-2014-8244"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2014-8244","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2014"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2014-8246"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2014-8243"},"products":["n/a"],"published":"2014-11-01","related":[{"cvss_score":3.3,"headline":"Information disclosure in n/a","id":"CVE-2014-8243","kev_date_added":null,"published":"2014-11-01"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive information or modify data on Linksys SMART WiFi routers via a JNAP action in an HTTP request.","url":"https://insights.sbomify.com/CVE-2014-8244/"}