{"answers":{"affected":"2 open source packages ship an affected version, including SafeURL-Python and safeurl-python.","exploited":"There is no known exploitation of GHSA-373w-rj84-pv6x in the wild and no public exploit code.","fix":"Upgrade SafeURL-Python to 1.3 or later.","what":"GHSA-373w-rj84-pv6x is a server-side request forgery vulnerability in SafeURL-Python, published on 29 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-373w-rj84-pv6x and fix it if it is affected.\n\nWhat it is: GHSA-373w-rj84-pv6x is a server-side request forgery vulnerability in SafeURL-Python, published on 29 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-373w-rj84-pv6x in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- SafeURL-Python (PyPI): affected all versions; fixed in 1.3\n- safeurl-python (PyPI): affected all versions; fixed in 1.3\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/GHSA-373w-rj84-pv6x/ (Markdown: https://insights.sbomify.com/GHSA-373w-rj84-pv6x/index.md)","id":"GHSA-373w-rj84-pv6x","markdown":"https://insights.sbomify.com/GHSA-373w-rj84-pv6x/index.md","name":"GHSA-373w-rj84-pv6x","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Python URL validation library","requires_auth":"none","summary":"Attackers can bypass hostname blocklists in SafeURL-Python by using FQDNs, enabling SSRF attacks against specifically blocked hosts.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Description\nIf a hostname was blacklisted, it was possible to bypass the blacklist by requesting the FQDN of the host (e.g. adding `.` to the end).\n\n### Impact\nThe main purpose of this library is to block requests to internal/private IPs and these cannot be bypassed using this finding. But if a library user had specifically set certain hostnames as blocked, then an attacker would be able to circumvent that block to cause SSRFs to request those hostnames.\n\n### Patches\nFixed by https://github.com/IncludeSecurity/safeurl-python/pull/6\n\n### Credit\nhttps://github.com/Sim4n6","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"SafeURL-Python's hostname blocklist does not block FQDNs","id":"GHSA-373w-rj84-pv6x","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":["1.3"],"introduced":["0"],"last_affected":[],"package":"SafeURL-Python","purl":null,"source":"GHSA-373w-rj84-pv6x"},{"ecosystem":"PyPI","fixed":["1.3"],"introduced":["0"],"last_affected":[],"package":"safeurl-python","purl":"pkg:pypi/safeurl-python","source":"GHSA-373w-rj84-pv6x"}],"products":null,"published":"2023-06-29","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass hostname blocklists in SafeURL-Python by using FQDNs, enabling SSRF attacks against specifically blocked hosts.","url":"https://insights.sbomify.com/GHSA-373w-rj84-pv6x/"}