Session hijacking via JWT-bearing file URLs
Published Mar 12, 2024 · Updated Aug 2, 2024
Sensitive-token exposure in Directus before 10.10.0 allows local users with log access to hijack sessions through logged /files URLs. The Studio files view places its JWT in a GET query string, causing web server logs and browser history to retain the credential in URL records. Exploitation requires access to those records, and a stolen active token grants the victim's Directus permissions until the session ends.
Summary
What happened
Sensitive-token exposure in Directus before 10.10.0 allows local users with log access to hijack sessions through logged /files URLs. The Studio files view places its JWT in a GET query string, causing web server logs and browser history to retain the credential in URL records. Exploitation requires access to those records, and a stolen active token grants the victim's Directus permissions until the session ends.
The record
- CVE
- CVE-2024-28238
- Published
- Mar 12, 2024
- Updated
- Aug 2, 2024
- Vendor
- Directus
- Product
- Directus
- Classifications
- CWE-200, CWE-598, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 12, 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
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