NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

@misskey-dev/summaly allows IP Filter Bypass via RedirectGHSA-jqx4-9gpq-rppm

MEDIUMFix: misskey-dev/summaly@dfe6451

GHSA-jqx4-9gpq-rppm is a medium-severity (CVSS 5.3) vulnerability in @misskey-dev/summaly. A fix is available for @misskey-dev/summaly — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of May 6, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@misskey-dev/summalynpm
12Kdownloads / week

Description

Summary

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/

Impact

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@misskey-dev/summaly≥ 5.1.0&&< 5.2.15.2.1npm install @misskey-dev/summaly@5.2.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @misskey-dev/summaly, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @misskey-dev/summaly to 5.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqx4-9gpq-rppm is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Summary 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 Summal
O3 Security · Impact-Aware SCA

Is GHSA-jqx4-9gpq-rppm in your dependencies?

Find it across npm, including transitive dependencies.

@misskey-dev/summaly allows IP Filter Bypass via Redirect