{"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-0904 in the wild and no public exploit code.","fix":"Upgrade private_address_check to 0.4.0 or later.","what":"CVE-2017-0904 is a high-severity server-side request forgery vulnerability in jtdowney private_address_check ruby gem, published on 13 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-0904 and fix it if it is affected.\n\nWhat it is: CVE-2017-0904 is a high-severity server-side request forgery vulnerability in jtdowney private_address_check ruby gem, published on 13 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-0904 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.0\n- private_address_check (RubyGems): affected all versions; fixed in 0.4.0\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-0904/ (Markdown: https://insights.sbomify.com/CVE-2017-0904/index.md)","id":"CVE-2017-0904","markdown":"https://insights.sbomify.com/CVE-2017-0904/index.md","name":"CVE-2017-0904","record":{"aliases":["GHSA-hxhj-hp9m-qwc4"],"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":"The private_address_check gem fails to block private IPs due to OS-dependent DNS resolution, allowing attackers to bypass SSRF protections.","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":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"},{"id":"CWE-242","name":"Use of Inherently Dangerous Function"}],"description":"The private_address_check ruby gem before 0.4.0 is vulnerable to a bypass due to use of Ruby's Resolv.getaddresses method, which is OS-dependent and should not be relied upon for security measures, such as when used to blacklist private network addresses 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 vulnerable to bypass of Resolv.getaddresses method","id":"CVE-2017-0904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"ssrf","year":"2017"},"n_packages":2,"n_references":5,"next":{"headline":"Recurly gem Server-Side Request Forgery in Resource#find method","id":"CVE-2017-0905"},"packages":[{"ecosystem":"RubyGems","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"private_address_check","purl":null,"source":"GHSA-hxhj-hp9m-qwc4"},{"ecosystem":"RubyGems","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"private_address_check","purl":"pkg:gem/private_address_check","source":"GHSA-hxhj-hp9m-qwc4"}],"prev":{"headline":"RubyGems vulnerable to Deserialization of Untrusted Data","id":"CVE-2017-0903"},"products":["private_address_check ruby gem"],"published":"2017-11-13","related":[{"cvss_score":9.8,"headline":"private_address_check contains Incomplete List of Disallowed Inputs","id":"CVE-2017-0909","kev_date_added":null,"published":"2017-11-16"},{"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-17","vendors":["jtdowney"]},"summary":"The private_address_check gem fails to block private IPs due to OS-dependent DNS resolution, allowing attackers to bypass SSRF protections.","url":"https://insights.sbomify.com/CVE-2017-0904/"}