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.
Original description
The description as published by the source.
Sanic before 0.5.1 allows reading arbitrary files with directory traversal, as demonstrated by the /static/..%2f substring.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
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.
Path traversal (CWE-22) exists in sanic.
Check the vendor advisory for the affected versions of sanic.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 0.5.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade sanic to 0.5.1ステージング環境で 0.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- report github.com
- web github.com