Authorization bypass via expired assertion reuse
Published Feb 11, 2024 · Updated Apr 24, 2025
Insufficient session expiration in handnot2 Samly before 1.4.0 allows remote attackers to retain access through expired SAML assertions. Samly.State.Store.get_assertion/3 returns cached assertions from ETS or the Plug session without comparing the subject notonorafter timestamp with the current time. A previously established SAML session is required, and Samly.AuthHandler continues authorizing the cached identity after its assertion expires.
Summary
What happened
Insufficient session expiration in handnot2 Samly before 1.4.0 allows remote attackers to retain access through expired SAML assertions. Samly.State.Store.get_assertion/3 returns cached assertions from ETS or the Plug session without comparing the subject notonorafter timestamp with the current time. A previously established SAML session is required, and Samly.AuthHandler continues authorizing the cached identity after its assertion expires.
The record
- CVE
- CVE-2024-25718
- Published
- Feb 11, 2024
- Updated
- Apr 24, 2025
- Vendor
- handnot2
- Product
- Samly
- Classifications
- CWE-613, CWE-400, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2024CVE publishedPublication date reported by the CVE source.
- Apr 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo