Session fixation
### Impact 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. ### Workarounds Call `Plug.Conn.configure_session(conn, renew: true)` periodically and after privilege change. A custom authorization plug can be written where the `create/3` method should return the `conn` only after `Plug.Conn.configure_session/2` have been called on it. ### References https://github.com/danschultzer/pow/commit/578ffd3d8bb8e8a26077b644222186b108da474f https://www.owasp.org/index.php/Session_fixation
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-5205US | medium5.4 | — | ||
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, s… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/danschultzer/powPACKAGE
- https://github.com/danschultzer/pow/blob/master/CHANGELOG.md#v1016-2020-01-07WEB
- https://github.com/danschultzer/pow/commit/578ffd3d8bb8e8a26077b644222186b108da474fWEB
- https://github.com/danschultzer/pow/security/advisories/GHSA-v2wf-c3j6-wpvwWEB
- https://nvd.nist.gov/vuln/detail/CVE-2020-5205ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan