← Back
CVE-2017-16762
high
CVSS 7.5
Path Traversal in sanic (CVE-2017-16762)
Summary
path traversal in sanic (CVE-2017-16762). Confidential information can be exposed externally. Mitigation: upgrade to `0.5.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2017-16762** has been found in sanic.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade sanic to **0.5.1** or later.
If unsure, ask your IT team or search "sanic CVE-2017-16762" on the vendor's site.
CVE-2017-16762 (sanic) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `0.5.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
**Path traversal** (CWE-22) exists in sanic.
📍 Affected scope
sanic — .
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.5.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 'sanic' .` 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 'sanic' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `sanic` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade sanic to 0.5.1ステージング環境で 0.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
sanic
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.1"}]}]