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