Directus vulnerabilities

Directus contains an authenticated SQL injection vulnerability in the collection creation flow when the instance uses PostgreSQL with PostGIS enabled. An administrator can create a collection with a geometry field whose fields[].type value starts with 'geometry' but contains attacker-controlled SQL syntax after the geometry subtype. This issue affects Directus before 12.1.0.

In Directus prior to version 12.0.0, when response caching is enabled, the cache-key derivation omits authorization context such as share tokens, roles, and policies. This allows different users or anonymous clients requesting the same URL to receive a cached response without permission re-evaluation.

In Directus prior to version 12.0.0, the SSRF protection on the file-import-from-URL feature can be bypassed using the address 0.0.0.0 because the system treats it as a keyword for local interfaces but never blocks the literal address. On Linux and macOS, connecting to 0.0.0.0 reaches localhost, allowing an authenticated user with file-upload rights to fetch internal services via the /files/import endpoint and retrieve the response as a downloadable file.

In Directus prior to 11.17.0, aggregate functions on conceal fields return raw values instead of masked placeholders. Authenticated users with read access can extract concealed values including API tokens and 2FA secrets.

Directus before version 11.17.0 does not deduplicate resolver invocations in GraphQL queries. An authenticated user can exploit GraphQL aliasing to repeat expensive relational queries many times, causing database overload and server resource exhaustion.

In Directus before version 11.16.1, despite disabling GraphQL introspection (GRAPHQL_INTROSPECTION=false), the server_specs_graphql resolver on the /graphql/system endpoint still returned the schema in SDL format. This allowed bypassing the introspection control and exposing database structure (collection names, field names, types, and relationships) to unauthenticated users at the public level and to authenticated users at their permission level.

Directus prior to 11.16.1 has a vulnerability in the TUS resumable upload endpoint (/files/tus) that allows an authenticated user with basic file upload permissions to overwrite arbitrary existing files by UUID. The TUS controller performs only collection-level authorization, bypassing row-level access rules.

Directus prior to version 11.16.1 is vulnerable to an open redirect via the 'redirect' parameter on the /admin/tfa-setup page. An administrator who has not configured 2FA yet, after visiting a crafted URL and completing the 2FA setup, is redirected to an attacker-controlled external domain without any validation.

Directus prior to version 11.16.1 contains an open redirect vulnerability in the login redirection logic. The isLoginRedirectAllowed function fails to correctly identify certain malformed URLs as external, allowing attackers to bypass redirect allow-list validation and redirect users to arbitrary external domains upon successful authentication.

In Directus prior to 11.16.0, an SSRF protection bypass was found using IPv4-Mapped IPv6 address notation, allowing requests to local and private networks.

In Directus prior to 11.17.0, the SSO login pages lack the Cross-Origin-Opener-Policy (COOP) header. An attacker can intercept and redirect the OAuth authorization flow to a controlled OAuth client, stealing access to the victim's account.

In Directus, from version 10.3.0 to 10.5.0, permission filters are not properly checked when using GraphQL subscriptions. This leads to unauthorized users receiving events they should not have access to.