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