Samly up to 1.3.x on Elixir Samly.State.Store.get_assertion session expiration
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Samly up to 1.3.x on Elixir. It has been classified as problematic. This affects the function Samly.State.Store.get_assertion
. The manipulation leads to session expiration.
This vulnerability is uniquely identified as CVE-2024-25718. There is no exploit available.
It is recommended to upgrade the affected component.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Details
A vulnerability was found in Samly up to 1.3.x on Elixir and classified as problematic. Affected by this issue is the function Samly.State.Store.get_assertion
. The manipulation with an unknown input leads to a session expiration vulnerability. Using CWE to declare the problem leads to CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." Impacted is confidentiality. CVE summarizes:
In the Samly package before 1.4.0 for Elixir, Samly.State.Store.get_assertion/3 can return an expired session, which interferes with access control because Samly.AuthHandler uses a cached session and does not replace it, even after expiry.
The weakness was published 02/11/2024. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2024-25718 since 02/11/2024. There are known technical details, but no exploit is available.
Upgrading to version 1.4.0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-0647). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 9.1
CNA Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Session expirationCWE: CWE-613
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Samly 1.4.0
Patch: github.com
Timeline
02/11/2024 🔍02/11/2024 🔍
02/11/2024 🔍
06/08/2025 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2024-25718 (🔍)
GCVE (CVE): GCVE-0-2024-25718
GCVE (VulDB): GCVE-100-253400
EUVD: 🔍
Entry
Created: 02/11/2024 09:26 AMUpdated: 06/08/2025 06:16 PM
Changes: 02/11/2024 09:26 AM (40), 08/02/2024 12:53 PM (27), 10/22/2024 09:18 AM (11), 06/08/2025 06:16 PM (1)
Complete: 🔍
Cache ID: 18:ED4:40
No comments yet. Languages: en.
Please log in to comment.