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