← Back
GHSA-52vm-mxx8-f227
Path Traversal in phantom-audio (GHSA-52vm-mxx8-f227)
Summary
path traversal in phantom-audio (GHSA-52vm-mxx8-f227). Confidential information can be exposed externally. Exploitable via ``PHANTOM_OUTPUT_DIR``. Mitigation: upgrade to `1.3.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-52vm-mxx8-f227** has been found in phantom-audio.
Attackers can target a specific entry point like ``PHANTOM_OUTPUT_DIR`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade phantom-audio to **1.3.1** or later.
If unsure, ask your IT team or search "phantom-audio GHSA-52vm-mxx8-f227" on the vendor's site.
GHSA-52vm-mxx8-f227 (phantom-audio) — CWE-22 /
Attack vector: local / unauthenticated / no user interaction
Attack surface: `PHANTOM_OUTPUT_DIR` / `__startup.lua` / `PHANTOM_AUDIO_DIR`
Patched: `1.3.1` — apply immediately
Workaround: Set `PHANTOM_OUTPUT_DIR` (and optionally `PHANTOM_AUDIO_DIR`) to dedicated directories before starting the server.
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 phantom-audio. Attackers reach the vulnerable code path via ``PHANTOM_OUTPUT_DIR`` without authentication.
📍 Affected scope
phantom-audio — . Attack surface: `PHANTOM_OUTPUT_DIR` / `__startup.lua` / `PHANTOM_AUDIO_DIR`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.3.1**.
🛡️ Workaround
Workaround: Set `PHANTOM_OUTPUT_DIR` (and optionally `PHANTOM_AUDIO_DIR`) to dedicated directories before starting the server.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'phantom-audio' .` 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 'phantom-audio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `phantom-audio` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Set `PHANTOM_OUTPUT_DIR` (and optionally `PHANTOM_AUDIO_DIR`) to dedicated directories before starting the server.パッチが適用されるまでの応急処置として、Set `PHANTOM_OUTPUT_DIR` (and optionally `PHANTOM_AUDIO_DIR`) to dedicated directories before starting the server. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade phantom-audio to 1.3.1ステージング環境で 1.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
phantom-audio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.1"}]}]
PyPI
phantom-audio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.1"}]}]