CVSS: 4.2EPSS: 0%CPEs: 1EXPL: 0CVE-2024-47822 – Access token from query string is inserted into logs in Directus
https://notcve.org/view.php?id=CVE-2024-47822
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`. • https://github.com/directus/directus/security/advisories/GHSA-vw58-ph65-6rxp • CWE-532: Insertion of Sensitive Information into Log File •
CVSS: 5.0EPSS: 0%CPEs: 2EXPL: 0CVE-2024-46990 – SSRF Loopback IP filter bypass in directus
https://notcve.org/view.php?id=CVE-2024-46990
Directus is a real-time API and App dashboard for managing SQL database content. When relying on blocking access to localhost using the default `0.0.0.0` filter a user may bypass this block by using other registered loopback devices (like `127.0.0.2` - `127.127.127.127`). This issue has been addressed in release versions 10.13.3 and 11.1.0. Users are advised to upgrade. Users unable to upgrade may block this bypass by manually adding the `127.0.0.0/8` CIDR range which will block access to any `127.X.X.X` ip instead of just `127.0.0.1`. • https://github.com/directus/directus/commit/4aace0bbe57232e38cd6a287ee475293e46dc91b https://github.com/directus/directus/commit/769fa22797bff5a9231599883b391e013f122e52 https://github.com/directus/directus/commit/8cbf943b65fd4a763d09a5fdbba8996b1e7797ff https://github.com/directus/directus/commit/c1f3ccc681595038d094ce110ddeee38cb38f431 https://github.com/directus/directus/security/advisories/GHSA-68g8-c275-xf2m • CWE-284: Improper Access Control •
CVSS: 7.4EPSS: 0%CPEs: 2EXPL: 0CVE-2024-45596 – Directus's session is cached for OpenID and OAuth2 if `redirect` is not used
https://notcve.org/view.php?id=CVE-2024-45596
Directus is a real-time API and App dashboard for managing SQL database content. An unauthenticated user can access credentials of last authenticated user via OpenID or OAuth2 where the authentication URL did not include redirect query string. This happens because on that endpoint for both OpenId and Oauth2 Directus is using the respond middleware, which by default will try to cache GET requests that met some conditions. Although, those conditions do not include this scenario, when an unauthenticated request returns user credentials. This vulnerability is fixed in 10.13.3 and 11.1.0. • https://github.com/directus/directus/commit/4aace0bbe57232e38cd6a287ee475293e46dc91b https://github.com/directus/directus/commit/769fa22797bff5a9231599883b391e013f122e52 https://github.com/directus/directus/security/advisories/GHSA-cff8-x7jv-4fm8 • CWE-524: Use of Cache Containing Sensitive Information •
CVSS: 4.1EPSS: 0%CPEs: 1EXPL: 0CVE-2024-6534 – Directus 10.13.0 - Insecure object reference via PATH presets
https://notcve.org/view.php?id=CVE-2024-6534
Directus v10.13.0 allows an authenticated external attacker to modify presets created by the same user to assign them to another user. This is possible because the application only validates the user parameter in the 'POST /presets' request but not in the PATCH request. When chained with CVE-2024-6533, it could result in account takeover. • https://directus.io https://fluidattacks.com/advisories/capaldi • CWE-639: Authorization Bypass Through User-Controlled Key •