Vulnerability in ash_authentication_phoenix (CVE-2025-4754)
Summary
Vulnerability in ash_authentication_phoenix (CVE-2025-4754). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.10.0 or later.
Original description
The description as published by the source.
Summary
Insufficient Session Expiration vulnerability in team-alembic ash_authentication_phoenix allows a session token captured before sign-out to remain usable afterwards.
The default sign_out/2 that AshAuthentication.Phoenix.Controller injects into an application's auth controller only calls Plug.Conn.clear_session/1. It never revokes the stored session or bearer tokens, so a token obtained before sign-out, through script injection, interception or device theft, keeps authenticating until its own expiry. Changing the password still revokes it.
This issue affects ash_authentication_phoenix: from 0.1.0 before 2.10.0.
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-2025-4754 has been found in ash_authentication_phoenix.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ash_authentication_phoenix to 2.10.0 or later.
If unsure, ask your IT team or search "ash_authentication_phoenix CVE-2025-4754" on the vendor's site.
CVE-2025-4754 (ash_authentication_phoenix) — CWE-613
Patched: 2.10.0 — 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-613) exists in ash_authentication_phoenix.
Check the vendor advisory for the affected versions of ash_authentication_phoenix.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.10.0.
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 'ash_authentication_phoenix' . 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 'ash_authentication_phoenix' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ash_authentication_phoenixを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ash_authentication_phoenix to 2.10.0ステージング環境で 2.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- package hex.pm
- patch github.com
- patch github.com
- web cna.erlef.org
- web osv.dev
- web github.com