Vulnerability in pow (CVE-2020-5205)
Summary
Vulnerability in pow (CVE-2020-5205). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.0.16 or later.
Original description
The description as published by the source.
In Pow (Hex package) before 1.0.16, the use of Plug.Session in Pow.Plug.Session is susceptible to session fixation attacks if a persistent session store is used for Plug.Session, such as Redis or a database. Cookie store, which is used in most Phoenix apps, doesn't have this vulnerability.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2020-5205 has been found in pow.
Risk of unauthorized operations or information disclosure.
What to do: upgrade pow to 1.0.16 or later.
If unsure, ask your IT team or search "pow CVE-2020-5205" on the vendor's site.
CVE-2020-5205 (pow) — CWE-384
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.0.16 — 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.
A vulnerability (CWE-384) exists in pow.
Check the vendor advisory for the affected versions of pow.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.16.
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 'pow' . 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 'pow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
powを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pow to 1.0.16ステージング環境で 1.0.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com