First published: Tue Oct 08 2024(Updated: )
Directus is a real-time API and App dashboard for managing SQL database content. Access tokens from query strings are not redacted and are potentially exposed in system logs which may be persisted. The access token in `req.query` is not redacted when the `LOG_STYLE` is set to `raw`. If these logs are not properly sanitized or protected, an attacker with access to it can potentially gain administrative control, leading to unauthorized data access and manipulation. This impacts systems where the `LOG_STYLE` is set to `raw`. The `access_token` in the query could potentially be a long-lived static token. Users with impacted systems should rotate their static tokens if they were provided using query string. This vulnerability has been patched in release version 10.13.2 and subsequent releases as well. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Directus | <10.13.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-47822 is considered a high severity vulnerability due to the potential exposure of sensitive access tokens.
To mitigate CVE-2024-47822, ensure that the LOG_STYLE is not set to 'raw' to prevent access tokens from being logged.
CVE-2024-47822 can lead to unauthorized access if an attacker gains access to logs containing unredacted access tokens.
CVE-2024-47822 affects Directus versions before 10.13.2.
A workaround for CVE-2024-47822 includes using alternative logging configurations that do not expose sensitive information.