# CVE-2024-39699: Directus has a Blind SSRF On File Import

> Attackers can bypass SSRF protections via redirects during file import to access internal network resources in Directus.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-8p72-rcq4-h6pw

## What is CVE-2024-39699?

CVE-2024-39699 is a medium-severity server-side request forgery vulnerability in Monospace Directus, published on 8 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directus is a real-time API and App dashboard for managing SQL database content. There was already a reported SSRF vulnerability via file import. It was fixed by resolving all DNS names and checking if the requested IP is an internal IP address. However it is possible to bypass this security measure and execute a SSRF using redirects. Directus allows redirects when importing file from the URL and does not check the result URL. Thus, it is possible to execute a request to an internal IP, for example to 127.0.0.1. However, it is blind SSRF, because Directus also uses response interception technique to get the information about the connect from the socket directly and it does not show a response if the IP address is internal. This vulnerability is fixed in 10.9.3.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@directus/api` | npm | All versions | 17.1.0 |
| `@directus/api` | npm | All versions | 17.1.0 |

Products: Monospace Directus.

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

Upgrade @directus/api to 17.1.0 or later.

## Is CVE-2024-39699 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39699 exists.

## 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-39699 and fix it if it is affected.

What it is: CVE-2024-39699 is a medium-severity server-side request forgery vulnerability in Monospace Directus, published on 8 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39699 exists.

Affected packages and fixed versions:
- @directus/api (npm): affected all versions; fixed in 17.1.0
- @directus/api (npm): affected all versions; fixed in 17.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-39699/ (Markdown: https://insights.sbomify.com/CVE-2024-39699/index.md)
```

## Sources

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

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