CVE-2024-34709
published 2024-05-14CVE-2024-34709: Directus is a real-time API and App dashboard for managing SQL database content. Prior to 10.11.0, session tokens function like the other JWT tokens where they…
PriorityP431medium5.4CVSS 3.1
AVNACHPRLUIRSUCHILAN
EPSS
0.45%
35.9th percentile
Directus is a real-time API and App dashboard for managing SQL database content. Prior to 10.11.0, session tokens function like the other JWT tokens where they are not actually invalidated when logging out. The `directus_session` gets destroyed and the cookie gets deleted but if the cookie value is captured, it will still work for the entire expiry time which is set to 1 day by default. Making it effectively a long lived unrevokable stateless token instead of the stateful session token it was meant to be. This vulnerability is fixed in 10.11.0.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| directus | directus | — | — |
| directus | directus | >= 10.10.0 < 10.11.0 | 10.11.0 |
| monospace | directus | < 10.11.0 | 10.11.0 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Directus Lacks Session Tokens Invalidation
osv·2024-05-13
CVE-2024-34709 [MEDIUM] Directus Lacks Session Tokens Invalidation
Directus Lacks Session Tokens Invalidation
### Summary
Currently session tokens function like the other JWT tokens where they are not actually invalidated when logging out. The `directus_session` gets destroyed and the cookie gets deleted but if you captured the cookie value it will still work for the entire expiry time which is set to 1 day by default. Making it effectively a long lived unrevokable stateless token instead of the stateful session token it was meant to be.
When authenticating a session token JWT, Directus should also check whether the associated `directus_session` both still exists and has not expired (although the token should expire at the same time or before the session) to ensure leaked tokens are not valid indefinitely.
## Steps to reproduce
- Copy the current sessio
GHSA
Directus Lacks Session Tokens Invalidation
ghsa·2024-05-13
CVE-2024-34709 [MEDIUM] CWE-613 Directus Lacks Session Tokens Invalidation
Directus Lacks Session Tokens Invalidation
### Summary
Currently session tokens function like the other JWT tokens where they are not actually invalidated when logging out. The `directus_session` gets destroyed and the cookie gets deleted but if you captured the cookie value it will still work for the entire expiry time which is set to 1 day by default. Making it effectively a long lived unrevokable stateless token instead of the stateful session token it was meant to be.
When authenticating a session token JWT, Directus should also check whether the associated `directus_session` both still exists and has not expired (although the token should expire at the same time or before the session) to ensure leaked tokens are not valid indefinitely.
## Steps to reproduce
- Copy the current sessio
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/directus/directus/commit/a6172f8a6a0f31a6bf4305a090de172ebfb63bcfhttps://github.com/directus/directus/security/advisories/GHSA-g65h-35f3-x2w3https://github.com/directus/directus/commit/a6172f8a6a0f31a6bf4305a090de172ebfb63bcfhttps://github.com/directus/directus/security/advisories/GHSA-g65h-35f3-x2w3
2024-05-14
Published