Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-4754: CWE-613 Insufficient Session Expiration in ash-project ash_authentication_phoenix

0
Low
VulnerabilityCVE-2025-4754cvecve-2025-4754cwe-613
Published: Tue Jun 17 2025 (06/17/2025, 14:31:37 UTC)
Source: CVE Database V5
Vendor/Project: ash-project
Product: ash_authentication_phoenix

Description

Insufficient Session Expiration vulnerability in ash-project ash_authentication_phoenix allows Session Hijacking. This vulnerability is associated with program files lib/ash_authentication_phoenix/controller.ex. This issue affects ash_authentication_phoenix until 2.10.0.

AI-Powered Analysis

AILast updated: 09/03/2025, 00:40:42 UTC

Technical Analysis

CVE-2025-4754 is a security vulnerability classified under CWE-613 (Insufficient Session Expiration) affecting the ash-project's ash_authentication_phoenix library, specifically in versions up to and including 2.10.0. The vulnerability arises from improper session expiration handling in the authentication mechanism implemented in the program file lib/ash_authentication_phoenix/controller.ex. Insufficient session expiration means that user sessions remain valid longer than intended or are not invalidated correctly after logout or inactivity, which can allow an attacker to hijack an active session. This session hijacking can lead to unauthorized access to user accounts or sensitive data within applications relying on this authentication library. The CVSS 4.0 base score is 2.3, indicating a low severity level, with the vector showing that the attack vector is network-based (AV:N), requires low attack complexity (AC:L), requires user interaction (UI:P), and partial privileges are not required (PR:N). The impact on confidentiality and integrity is low, with no impact on availability. No known exploits are currently in the wild, and no patches have been linked yet. The vulnerability primarily affects web applications using ash_authentication_phoenix for session management, which is a component in the Elixir programming ecosystem, often used for building scalable web applications.

Potential Impact

For European organizations, the impact of this vulnerability depends on their adoption of the ash_authentication_phoenix library within their web applications. Organizations using this library may face risks of session hijacking attacks, potentially leading to unauthorized access to user accounts and sensitive information. While the severity is low, attackers exploiting this vulnerability could bypass session expiration controls, especially in environments where session tokens are not rotated or invalidated properly. This could undermine user trust and lead to data breaches or unauthorized transactions. The risk is higher in sectors handling sensitive personal data, such as finance, healthcare, and government services, where session hijacking could facilitate identity theft or fraud. However, the low CVSS score and lack of known exploits suggest the immediate threat level is limited. Nonetheless, organizations should not ignore this vulnerability, as session management flaws are common attack vectors and could be chained with other vulnerabilities for more severe attacks.

Mitigation Recommendations

European organizations should take the following specific mitigation steps: 1) Upgrade to ash_authentication_phoenix version 2.10.1 or later once a patch is released addressing this vulnerability. 2) Implement strict session expiration policies at the application level, including setting short session timeouts and ensuring sessions are invalidated immediately upon logout or inactivity. 3) Employ additional security controls such as rotating session tokens on sensitive actions and using secure, HttpOnly, and SameSite cookie attributes to protect session cookies. 4) Monitor session activity for anomalies that could indicate hijacking attempts, such as concurrent sessions from different IP addresses or geolocations. 5) Conduct code reviews and penetration testing focused on session management to identify and remediate similar issues. 6) Educate developers on secure session handling best practices to prevent recurrence. 7) Consider implementing multi-factor authentication (MFA) to reduce the impact of compromised sessions.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
EEF
Date Reserved
2025-05-15T09:03:11.355Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68517cf5a8c921274385d335

Added to database: 6/17/2025, 2:34:29 PM

Last enriched: 9/3/2025, 12:40:42 AM

Last updated: 11/22/2025, 6:02:08 PM

Views: 37

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats