GHSA-JQX4-9GPQ-RPPM

Due to a validation error in got.scpaping, it is possible to use an HTTP redirect to avoid IP filtering.

Details

In 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.

PoC

With a simple Caddy webserver, you can get Summaly to summarize a page hosted via a local IP address:

@summaly-bypass-head {
    method HEAD
    path /summaly-bypass
}
@summaly-bypass-get {
    method GET
    path /summaly-bypass
}
header @summaly-bypass-head Content-Type "text/html"
respond @summaly-bypass-head 200
redir @summaly-bypass-get http://127.0.0.1:3080/

Using 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.

GHSA-JQX4-9GPQ-RPPM has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.2.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-JQX4-9GPQ-RPPM? GHSA-JQX4-9GPQ-RPPM is a medium-severity security vulnerability in @misskey-dev/summaly (npm), affecting versions >= 5.1.0, < 5.2.1. It is fixed in 5.2.1.
2. How severe is GHSA-JQX4-9GPQ-RPPM? GHSA-JQX4-9GPQ-RPPM has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @misskey-dev/summaly are affected by GHSA-JQX4-9GPQ-RPPM? @misskey-dev/summaly (npm) versions >= 5.1.0, < 5.2.1 is affected.
4. Is there a fix for GHSA-JQX4-9GPQ-RPPM? Yes. GHSA-JQX4-9GPQ-RPPM is fixed in 5.2.1. Upgrade to this version or later.
5. Is GHSA-JQX4-9GPQ-RPPM exploitable, and should I be worried? Whether GHSA-JQX4-9GPQ-RPPM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-JQX4-9GPQ-RPPM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-JQX4-9GPQ-RPPM? Upgrade @misskey-dev/summaly to 5.2.1 or later.