Information Disclosure in fluture-node (CVE-2022-24719)

Summary

vulnerability in fluture-node (CVE-2022-24719). Risk of unauthorized operations or information disclosure. Exploitable via ``followRedirects``. Mitigation: upgrade to `4.0.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2022-24719** has been found in fluture-node. Attackers can target a specific entry point like ``followRedirects`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade fluture-node to **4.0.2** or later. If unsure, ask your IT team or search "fluture-node CVE-2022-24719" on the vendor's site.

CVE-2022-24719 (fluture-node) — CWE-200 / Attack surface: `followRedirects` / `followRedirectsWith` Patched: `4.0.2` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

**information disclosure** (CWE-200) exists in fluture-node. Attackers reach the vulnerable code path via ``followRedirects`` without authentication.

📍 Affected scope

fluture-node — . Attack surface: `followRedirects` / `followRedirectsWith`.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **4.0.2**.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'fluture-node' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'fluture-node' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `fluture-node` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade fluture-node to 4.0.2
```
ステージング環境で 4.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm fluture-node

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.2"}]}]

PyPI request-util

[{"repo":"https:\/\/github.com\/fluture-js\/fluture-node","type":"GIT","events":[{"introduced":"0"},{"fixed":"0c99bc511533d48be17dc6bfe641f7d0aeb34d77"},{"fixed":"125e4474f910c1507f8ec3232848626fbc0f55c4"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

PyPI pyquest