Session hijacking via unrevoked logout tokens
Published May 13, 2024 · Updated Aug 2, 2024
Insufficient session expiration in Directus 10.10.0 and later, before 10.11.0, allows remote attackers to reuse captured session cookies. Token accountability accepts a session JWT without checking whether its directus_sessions row still exists and remains unexpired. Exploitation requires obtaining a user's cookie; logout deletes the session and browser cookie, but the stolen token retains the victim's permissions for its remaining lifetime.
Summary
What happened
Insufficient session expiration in Directus 10.10.0 and later, before 10.11.0, allows remote attackers to reuse captured session cookies. Token accountability accepts a session JWT without checking whether its directus_sessions row still exists and remains unexpired. Exploitation requires obtaining a user's cookie; logout deletes the session and browser cookie, but the stolen token retains the victim's permissions for its remaining lifetime.
The record
- CVE
- CVE-2024-34709
- Published
- May 13, 2024
- Updated
- Aug 2, 2024
- Vendor
- Directus
- Product
- Directus
- Classifications
- CWE-613, T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=>= 10.10.0, < 10.11.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
- Vendor post-logout token-reuse reproduction stepsproof of concept · demonstrated
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