CVE-2024-47822: Directus inserts access token from query string into logs

Published Oct 8, 2024
·
Updated

Summary Access token from query string is not redacted and is potentially exposed in system logs which may be persisted.

Details The access token in req.query is not redacted when the LOGSTYLE 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.

PoC 1. Set LOGLEVEL="raw" in the environment. 2. Send a request with the accesstoken in the query string. 3. Notice that the accesstoken in req.query is not redacted.

Impact It impacts systems where the LOGSTYLE is set to raw. The accesstoken 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.

Other sources

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 LOGSTYLE 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 LOGSTYLE is set to raw. The accesstoken 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.

NVD

Affected Software

2 affected componentsFixes available
npm/@directus/api<21.0.0
21.0.0
Monospace Directus Node.js<10.13.2

Event History

Oct 8, 2024
CVE Published
via MITRE·05:54 PM
Data Sourced
via MITRE·05:54 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeaknessAffected Software
Apr 14, 2025
Advisory Published
via GitHub·03:20 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-47822?

CVE-2024-47822 is considered a high severity vulnerability due to the potential exposure of sensitive access tokens.

2

How do I fix CVE-2024-47822?

To mitigate CVE-2024-47822, ensure that the LOG_STYLE is not set to 'raw' to prevent access tokens from being logged.

3

What impact does CVE-2024-47822 have on users?

CVE-2024-47822 can lead to unauthorized access if an attacker gains access to logs containing unredacted access tokens.

4

Which versions of Directus are affected by CVE-2024-47822?

CVE-2024-47822 affects Directus versions before 10.13.2.

5

Is there a workaround for CVE-2024-47822?

A workaround for CVE-2024-47822 includes using alternative logging configurations that do not expose sensitive information.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203