# CVE-2024-45596: Directus's session is cached for OpenID and OAuth2 if `redirect` is not used

> Unauthenticated users can access previous user credentials via cached OpenID/OAuth2 responses, potentially leading to account takeover.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Sep 2024
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-cff8-x7jv-4fm8

## What is CVE-2024-45596?

CVE-2024-45596 is a high-severity vulnerability in Monospace Directus, published on 10 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-524 (Use of Cache Containing Sensitive Information)

## Which versions are affected by CVE-2024-45596?

8 open source packages ship an affected version, including @directus/api and directus. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@directus/api` | npm | All versions | 21.0.1 |
| `@directus/api` | npm | All versions | 21.0.1 |
| `@directus/api` | npm | From 22.0.0 | 22.2.0 |
| `@directus/api` | npm | From 22.0.0 | 22.2.0 |
| `directus` | npm | All versions | 10.13.3 |
| `directus` | npm | All versions | 10.13.3 |
| `directus` | npm | From 11.0.0-rc.1 | 11.1.0 |
| `directus` | npm | From 11.0.0-rc.1 | 11.1.0 |

Products: Monospace Directus.

## How do I fix CVE-2024-45596?

Upgrade @directus/api to a fixed version for your release line: 21.0.1 or 22.2.0.

## Is CVE-2024-45596 being exploited?

There is no known exploitation of CVE-2024-45596 in the wild and no public exploit code.

## Other vulnerabilities in Monospace Directus

- [CVE-2022-26969](https://insights.sbomify.com/CVE-2022-26969/): Insecure default value for CORS configuration (critical 9.8)
- [CVE-2025-55746](https://insights.sbomify.com/CVE-2025-55746/): Directus allows unauthenticated file upload and file modification due to lacking input sanitization (critical 9.3)
- [CVE-2026-35408](https://insights.sbomify.com/CVE-2026-35408/): Directus is Missing Cross-Origin Opener Policy (high 8.7)
- [CVE-2026-61836](https://insights.sbomify.com/CVE-2026-61836/): Directus: Authorization-dependent response served from unsegmented cache key (high 8.6)
- [CVE-2025-30353](https://insights.sbomify.com/CVE-2025-30353/): Directus's webhook trigger flows can leak sensitive data (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45596 and fix it if it is affected.

What it is: CVE-2024-45596 is a high-severity vulnerability in Monospace Directus, published on 10 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-45596 in the wild and no public exploit code.

Affected packages and fixed versions:
- @directus/api (npm): affected all versions; fixed in 21.0.1
- @directus/api (npm): affected all versions; fixed in 21.0.1
- @directus/api (npm): affected from 22.0.0; fixed in 22.2.0
- @directus/api (npm): affected from 22.0.0; fixed in 22.2.0
- directus (npm): affected all versions; fixed in 10.13.3
- directus (npm): affected all versions; fixed in 10.13.3
- directus (npm): affected from 11.0.0-rc.1; fixed in 11.1.0
- directus (npm): affected from 11.0.0-rc.1; fixed in 11.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45596/ (Markdown: https://insights.sbomify.com/CVE-2024-45596/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45596
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45596
- OSV: https://osv.dev/vulnerability/CVE-2024-45596

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45596/
Summaries are generated and may contain mistakes; the official description above is the record.