Directus inserts access token from query string into logs

TRUNG BÌNH 4.2CVE-2024-47822 · GHSA-vw58-ph65-6rxp · Công bố 08/10/2024 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2024-47822 là lỗ hổng mức TRUNG BÌNH (CVSS 4.2) ảnh hưởng directus (monospace), @directus/api.
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.31%, cao hơn 24.0% các lỗ hổng khác.
Cách xử lý: cập nhật lên 10.13.2, 21.0.0 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
directus monospace	`< 10.13.2`	`10.13.2`
@directus/api npm	`< 21.0.0`	`21.0.0`

Mô tả

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 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.

PoC

Set LOG_LEVEL="raw" in the environment.
Send a request with the access_token in the query string.
Notice that the access_token in req.query is not redacted.

Impact

It 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.

Mô tả của NVD

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.