CVE-2024-25718: Critical severity Dropbox Samly Elixir vulnerability
In the Samly package before 1.4.0 for Elixir, Samly.State.Store.getassertion/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.
Other sources
In the Samly package before 1.4.0 for Elixir, Samly.State.Store.getassertion/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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
erlang/Samlyto a version that resolves this vulnerability.Fixed in 1.4.0
Event History
Frequently Asked Questions
What is the severity of CVE-2024-25718?
CVE-2024-25718 has been classified as a moderate severity vulnerability.
How do I fix CVE-2024-25718?
To fix CVE-2024-25718, upgrade the Samly package to version 1.4.0 or later.
What software is affected by CVE-2024-25718?
CVE-2024-25718 affects the Samly package for Elixir versions prior to 1.4.0.
What kind of vulnerability is CVE-2024-25718?
CVE-2024-25718 is a session management vulnerability that allows expired sessions to interfere with access control.
Who is the vendor for CVE-2024-25718?
The vendor for CVE-2024-25718 is Dropbox, which maintains the Samly package.