GHSA-3cjh-p6pw-jhv9

Suggest an improvement
Source
https://github.com/advisories/GHSA-3cjh-p6pw-jhv9
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/09/GHSA-3cjh-p6pw-jhv9/GHSA-3cjh-p6pw-jhv9.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-3cjh-p6pw-jhv9
Aliases
Published
2023-09-19T17:00:08Z
Modified
2023-11-08T04:13:28.354371Z
Severity
  • 6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
Summary
Pow Mnesia cache doesn't invalidate all expired keys on startup
Details

Use of Pow.Store.Backend.MnesiaCache is susceptible to session hijacking as expired keys are not being invalidated correctly on startup. A cache key may become expired when all Pow.Store.Backend.MnesiaCache instances have been shut down for a period that is longer than the keys' remaining TTL and the expired key won't be invalidated on startups.

Workarounds

The expired keys, including all expired sessions, can be manually invalidated by running:

:mnesia.sync_transaction(fn ->
  Enum.each(:mnesia.dirty_select(Pow.Store.Backend.MnesiaCache, [{{Pow.Store.Backend.MnesiaCache, :_, :_}, [], [:"$_"]}]), fn {_, key,  {_value, expire}} ->
    ttl = expire - :os.system_time(:millisecond)
    if ttl < 0, do: :mnesia.delete({Pow.Store.Backend.MnesiaCache, key})
  end)
end)

References

https://github.com/pow-auth/pow/commit/15dc525be03c466daa5d2119ca7acdec7b24ed17 https://github.com/pow-auth/pow/issues/713 https://github.com/pow-auth/pow/pull/714

References

Affected packages

Hex / pow

Package

Name
pow
Purl
pkg:hex/pow

Affected ranges

Type
SEMVER
Events
Introduced
1.0.14
Fixed
1.0.34