{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20489 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20489 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20489 is a critical authentication bypass vulnerability in n/a, published on 2 Mar 2020. 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-20489 and fix it if it is affected.\n\nWhat it is: CVE-2019-20489 is a critical authentication bypass vulnerability in n/a, published on 2 Mar 2020. 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-20489 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-20489/ (Markdown: https://insights.sbomify.com/CVE-2019-20489/index.md)","id":"CVE-2019-20489","markdown":"https://insights.sbomify.com/CVE-2019-20489/index.md","name":"CVE-2019-20489","record":{"aliases":["GHSA-rr49-pwf2-62mg"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"NETGEAR wireless router","requires_auth":"none","summary":"Attackers can bypass authentication on NETGEAR routers via a cookie manipulation flaw, leading to remote device compromise.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wnr1000_firmware","vendor":"netgear"}],"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-287","name":"Improper Authentication"}],"description":"An issue was discovered on NETGEAR WNR1000V4 1.1.0.54 devices. The web management interface (setup.cgi) has an authentication bypass and other problems that ultimately allow an attacker to remotely compromise the device from a malicious webpage. The attacker sends an FW_remote.htm\u0026todo=cfg_init request without a cookie, reads the Set-Cookie header in the 401 Unauthorized response, and then repeats the FW_remote.htm\u0026todo=cfg_init request with the specified cookie.","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":"Auth bypass in n/a","id":"CVE-2019-20489","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2019-20490"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-20488"},"products":["n/a"],"published":"2020-03-02","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-20488","kev_date_added":null,"published":"2020-03-02"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2013-3316","kev_date_added":null,"published":"2020-01-29"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2013-3317","kev_date_added":null,"published":"2020-01-29"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-20487","kev_date_added":null,"published":"2020-03-02"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-20486","kev_date_added":null,"published":"2020-03-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":"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":"Attackers can bypass authentication on NETGEAR routers via a cookie manipulation flaw, leading to remote device compromise.","url":"https://insights.sbomify.com/CVE-2019-20489/"}