{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12510 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12510 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12510 is a critical authentication bypass vulnerability in n/a, published on 24 Feb 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-12510 and fix it if it is affected.\n\nWhat it is: CVE-2019-12510 is a critical authentication bypass vulnerability in n/a, published on 24 Feb 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-12510 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-12510/ (Markdown: https://insights.sbomify.com/CVE-2019-12510/index.md)","id":"CVE-2019-12510","markdown":"https://insights.sbomify.com/CVE-2019-12510/index.md","name":"CVE-2019-12510","record":{"aliases":["GHSA-393h-j526-4h79"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"NETGEAR Nighthawk router","requires_auth":"none","summary":"Attackers can bypass authentication on the SOAP API by spoofing the X-Forwarded-For header, allowing them to view and modify router settings.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nighthawk_x10-r9000_firmware","vendor":"netgear"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"In NETGEAR Nighthawk X10-R900 prior to 1.0.4.26, an attacker may bypass all authentication checks on the device's \"NETGEAR Genie\" SOAP API (\"/soap/server_sa\") by supplying a malicious X-Forwarded-For header of the device's LAN IP address (192.168.1.1) in every request. As a result, an attacker may modify almost all of the device's settings and view various configuration settings.","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 Via X-Forwarded-For Header in SOAP API","id":"CVE-2019-12510","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":"Root Command Injection via MAC Address in SOAP API","id":"CVE-2019-12511"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-12507"},"products":["n/a"],"published":"2020-02-24","related":[{"cvss_score":9.8,"headline":"Root Command Injection via MAC Address in SOAP API","id":"CVE-2019-12511","kev_date_added":null,"published":"2020-02-24"},{"cvss_score":6.1,"headline":"Stored XSS via X-Forwarded-For Header During Incorrect Login","id":"CVE-2019-12512","kev_date_added":null,"published":"2020-02-24"},{"cvss_score":6.1,"headline":"Stored XSS via DHCP Discover Request Hostname","id":"CVE-2019-12513","kev_date_added":null,"published":"2020-02-24"}],"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-04","vendors":["n/a"]},"summary":"Attackers can bypass authentication on the SOAP API by spoofing the X-Forwarded-For header, allowing them to view and modify router settings.","url":"https://insights.sbomify.com/CVE-2019-12510/"}