← Back
DEBIAN-CVE-2025-59465
Vulnerability in nodejs (DEBIAN-CVE-2025-59465)
Summary
vulnerability in nodejs (DEBIAN-CVE-2025-59465). Risk of unauthorized operations or information disclosure. Exploitable via ``HPACK``. Mitigation: upgrade to `12.22.12~dfsg-1~deb11u8` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **DEBIAN-CVE-2025-59465** has been found in nodejs.
Attackers can target a specific entry point like ``HPACK`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade nodejs to **12.22.12~dfsg-1~deb11u8** or later.
If unsure, ask your IT team or search "nodejs DEBIAN-CVE-2025-59465" on the vendor's site.
DEBIAN-CVE-2025-59465 (nodejs) —
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `HPACK` / `TLSSocket` / `ECONNRESET`
Patched: `12.22.12~dfsg-1~deb11u8` — 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
**A vulnerability** (unclassified) exists in nodejs. Attackers reach the vulnerable code path via ``HPACK`` without authentication.
📍 Affected scope
nodejs — . Attack surface: `HPACK` / `TLSSocket` / `ECONNRESET`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **12.22.12~dfsg-1~deb11u8**.
🛡️ 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 'nodejs' .` 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
-
1Identify exposure identify
grep -r 'nodejs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `nodejs` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade nodejs to 12.22.12~dfsg-1~deb11u8ステージング環境で 12.22.12~dfsg-1~deb11u8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Debian:11
nodejs
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.12~dfsg-1~deb11u8"}]}]
Debian:12
nodejs
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.20.4+dfsg-1~deb12u2"}]}]
Debian:13
nodejs
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.19.2+dfsg-1+deb13u1"}]}]
Debian:14
nodejs
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.22.0+dfsg+~cs22.19.6-1"}]}]