{"answers":{"affected":"2 open source packages ship an affected version, including @misskey-dev/summaly.","exploited":"There is no known exploitation of GHSA-jqx4-9gpq-rppm in the wild and no public exploit code.","fix":"Upgrade @misskey-dev/summaly to 5.2.1 or later.","what":"GHSA-jqx4-9gpq-rppm is a server-side request forgery vulnerability in @misskey-dev/summaly, published on 6 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-jqx4-9gpq-rppm and fix it if it is affected.\n\nWhat it is: GHSA-jqx4-9gpq-rppm is a server-side request forgery vulnerability in @misskey-dev/summaly, published on 6 May 2025. 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-jqx4-9gpq-rppm in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @misskey-dev/summaly (npm): affected from 5.1.0; fixed in 5.2.1\n- @misskey-dev/summaly (npm): affected from 5.1.0; fixed in 5.2.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/GHSA-jqx4-9gpq-rppm/ (Markdown: https://insights.sbomify.com/GHSA-jqx4-9gpq-rppm/index.md)","id":"GHSA-jqx4-9gpq-rppm","markdown":"https://insights.sbomify.com/GHSA-jqx4-9gpq-rppm/index.md","name":"GHSA-jqx4-9gpq-rppm","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Summaly npm library","requires_auth":"none","summary":"An attacker can bypass IP filtering via HTTP redirects to access internal network services and extract sensitive information.","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":"### Summary\nDue to a validation error in `got.scpaping`, it is possible to use an HTTP redirect to avoid IP filtering.\n\n### Details\nIn `got.scpaping`, Summaly first makes a HTTP `HEAD` request to the page being summarized. It then preforms private IP address checks on the `HEAD` response, then makes an additional HTTP `GET` request to the page being summarized. Unfortunately, since private IP address checks aren't performed on the `GET` response, the `GET` response can issue a HTTP redirect to a private IP address, which will succeed, regardless of if private IP addresses are allowed by Summaly.\n\n### PoC\nWith a simple Caddy webserver, you can get Summaly to summarize a page hosted via a local IP address:\n```caddy\n@summaly-bypass-head {\n    method HEAD\n    path /summaly-bypass\n}\n@summaly-bypass-get {\n    method GET\n    path /summaly-bypass\n}\nheader @summaly-bypass-head Content-Type \"text/html\"\nrespond @summaly-bypass-head 200\nredir @summaly-bypass-get http://127.0.0.1:3080/\n```\n\n### Impact\nUsing this bypass, an attacker can probe a victims internal network for HTTP services that aren't supposed to be exposed to the outside world. While they might only have read-only access through this, it may still be possible to extract sensitive information or be used to probe a network prior to attacking via other exploits without leaving a trace.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"@misskey-dev/summaly allows IP Filter Bypass via Redirect","id":"GHSA-jqx4-9gpq-rppm","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["5.2.1"],"introduced":["5.1.0"],"last_affected":[],"package":"@misskey-dev/summaly","purl":null,"source":"GHSA-jqx4-9gpq-rppm"},{"ecosystem":"npm","fixed":["5.2.1"],"introduced":["5.1.0"],"last_affected":[],"package":"@misskey-dev/summaly","purl":"pkg:npm/%40misskey-dev/summaly","source":"GHSA-jqx4-9gpq-rppm"}],"products":null,"published":"2025-05-06","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":"An attacker can bypass IP filtering via HTTP redirects to access internal network services and extract sensitive information.","url":"https://insights.sbomify.com/GHSA-jqx4-9gpq-rppm/"}