First published: Tue Mar 12 2024(Updated: )
### Impact When reaching the /files page, a JWT is passed via GET request. Inclusion of session tokens in URLs poses a security risk as URLs are often logged in various places (e.g., web server logs, browser history). Attackers gaining access to these logs may hijack active user sessions, leading to unauthorized access to sensitive information or actions on behalf of the user. ### Patches _Has the problem been patched? What versions should users upgrade to?_ ### Workarounds There's no workaround available. ### References _Are there any links users can visit to find out more?_
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
npm/directus | <10.10.0 | 10.10.0 |
Directus | <10.10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2024-28238 is potentially high due to security risks associated with including session tokens in URLs.
To fix CVE-2024-28238, ensure that JWT tokens are not passed through GET requests and instead use secure methods for session management.
CVE-2024-28238 affects Directus versions up to but not including 10.10.0.
The risks associated with CVE-2024-28238 include potential session hijacking if attackers gain access to logged URLs.
A possible workaround for CVE-2024-28238 is to restrict access to logs containing sensitive information and avoid using JWT in URLs.