{"answers":{"affected":"2 open source packages ship an affected version, including private_address_check. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-0909 in the wild and no public exploit code.","fix":"Upgrade private_address_check to 0.4.1 or later.","what":"CVE-2017-0909 is a critical server-side request forgery vulnerability in HackerOne private_address_check ruby gem, published on 16 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-0909 and fix it if it is affected.\n\nWhat it is: CVE-2017-0909 is a critical server-side request forgery vulnerability in HackerOne private_address_check ruby gem, published on 16 Nov 2017. 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-2017-0909 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- private_address_check (RubyGems): affected all versions; fixed in 0.4.1\n- private_address_check (RubyGems): affected all versions; fixed in 0.4.1\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-2017-0909/ (Markdown: https://insights.sbomify.com/CVE-2017-0909/index.md)","id":"CVE-2017-0909","markdown":"https://insights.sbomify.com/CVE-2017-0909/index.md","name":"CVE-2017-0909","record":{"aliases":["GHSA-3v3c-r5v2-68ph"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby SSRF protection gem","requires_auth":"none","summary":"An attacker can bypass SSRF protections in the private_address_check Ruby gem due to an incomplete blacklist of private network addresses.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"private_address_check","vendor":"private_address_check_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"description":"The private_address_check ruby gem before 0.4.1 is vulnerable to a bypass due to an incomplete blacklist of common private/local network addresses used to prevent server-side request forgery.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"private_address_check contains Incomplete List of Disallowed Inputs","id":"CVE-2017-0909","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"ssrf","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"Missing authorization in Zulip Server","id":"CVE-2017-0910"},"packages":[{"ecosystem":"RubyGems","fixed":["0.4.1"],"introduced":["0"],"last_affected":[],"package":"private_address_check","purl":null,"source":"GHSA-3v3c-r5v2-68ph"},{"ecosystem":"RubyGems","fixed":["0.4.1"],"introduced":["0"],"last_affected":[],"package":"private_address_check","purl":"pkg:gem/private_address_check","source":"GHSA-3v3c-r5v2-68ph"}],"prev":{"headline":"Critical severity vulnerability that affects recurly-api-client","id":"CVE-2017-0907"},"products":["private_address_check ruby gem"],"published":"2017-11-16","related":[{"cvss_score":8.1,"headline":"private_address_check vulnerable to bypass of Resolv.getaddresses method","id":"CVE-2017-0904","kev_date_added":null,"published":"2017-11-13"},{"cvss_score":3.7,"headline":"private_address_check contains race condition","id":"CVE-2018-3759","kev_date_added":null,"published":"2018-06-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-09-16","vendors":["HackerOne"]},"summary":"An attacker can bypass SSRF protections in the private_address_check Ruby gem due to an incomplete blacklist of private network addresses.","url":"https://insights.sbomify.com/CVE-2017-0909/"}