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