← Back
GHSA-382c-vx95-w3p5
Vulnerability in @jsonbored/gittensory-mcp (GHSA-382c-vx95-w3p5)
Summary
vulnerability in @jsonbored/gittensory-mcp (GHSA-382c-vx95-w3p5). Confidential information can be exposed externally. Exploitable via `GET /v1/contributors/`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-382c-vx95-w3p5** has been found in @jsonbored/gittensory-mcp.
Attackers can target a specific entry point like `GET /v1/contributors/` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "@jsonbored/gittensory-mcp GHSA-382c-vx95-w3p5" on the vendor's site.
GHSA-382c-vx95-w3p5 (@jsonbored/gittensory-mcp) — CWE-284 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /v1/contributors/ / GET /v1/contributors/{target}/profile / GET /v1/contributors/{target}/decision-pack / `gittensory_get_contributor_profile`
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-284) exists in @jsonbored/gittensory-mcp. Attackers reach the vulnerable code path via `GET /v1/contributors/` without authentication.
📍 Affected scope
@jsonbored/gittensory-mcp — . Attack surface: GET /v1/contributors/ / GET /v1/contributors/{target}/profile / GET /v1/contributors/{target}/decision-pack / `gittensory_get_contributor_profile`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 `GET /v1/contributors/` requests with malformed payloads or SQL meta-characters. Run `grep -r '@jsonbored/gittensory-mcp' .` 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 '@jsonbored/gittensory-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@jsonbored/gittensory-mcp` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /v1/contributors/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /v1/contributors/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against GET /v1/contributors/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@jsonbored/gittensory-mcp
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"0.1.0"}]}]