Team-alembic ash_authentication
Revoked session accepted because the session jti is never checked in AshAuthentication and AshAuthentication Phoenix
Insufficient Session Expiration vulnerability in team-alembic AshAuthentication and AshAuthentication Phoenix allows a revoked session to remain fully authenticated. A resource configured with session_identifier :jti and require_token_presence_for_authentication? disabled stores its session value as <jti>:<subject>. The jti is there so that signing out can revoke that one session. Neither reader consults it: AshAuthentication.Plug.Helpers.authenticate_resource_from_session/4 and AshAuthentication.Phoenix.LiveSession.on_mount/4 both split the value with split_identifier/2, discard the jti and pass the bare subject to AshAuthentication.subject_to_user/3, which reloads the record. The token-presence branch of each function does check its token, calling AshAuthentication.TokenResource.Actions.get_token/3 with the jti and the purpose user. Because the revocation record is never read, neither its revoked state nor its expiry constrains the session, so a session captured before sign-out keeps working. This issue affects ash_authentication: from 4.9.1 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14; ash_authentication_phoenix: from 2.10.0 before 2.17.4 and from 3.0.0-rc.0 before 3.0.0-rc.11.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.9.1, < 4.15.0
- >= 5.0.0-rc.0, < 5.0.0-rc.14
Fixed in 4.15.0, 5.0.0-rc.14
- >= fcaeb73f76f8f2e9aef8bf637690d2a20dd97596, < *
Fixed in *, a3f49f758f013d2ff086dd9c5ef2d94e921711b4, e28e911caa9728d76329afdb0fb26742ffe4eeef
- >= 2.10.0, < 2.17.4
- >= 3.0.0-rc.0, < 3.0.0-rc.11
Fixed in 2.17.4, 3.0.0-rc.11
- >= 0135217e34e621dac79ae3d9559aeee49304b0aa, < 0135217e34e621dac79ae3d9559aeee49304b0aa
- >= a3253fb4fc7145aeb403537af1c24d3a8d51ffb1, < *
Fixed in 0135217e34e621dac79ae3d9559aeee49304b0aa, *, f7ab005a2aac09707a25521653c94893d328cc52
Mitigation
Upgrade ash_authentication to 4.15.0 or 5.0.0-rc.14 or later.
Upgrade ash_authentication to * or a3f49f758f013d2ff086dd9c5ef2d94e921711b4 or e28e911caa9728d76329afdb0fb26742ffe4eeef or later.
Upgrade ash_authentication_phoenix to 2.17.4 or 3.0.0-rc.11 or later.
Upgrade ash_authentication_phoenix to 0135217e34e621dac79ae3d9559aeee49304b0aa or * or f7ab005a2aac09707a25521653c94893d328cc52 or later.
References
- Vendor advisory github.com/team-alembic/ash_authentication_pho…
- Vendor advisory github.com/team-alembic/ash_authentication/sec…
- Patch github.com/team-alembic/ash_authentication/com…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.