# CVE-2024-46990: SSRF Loopback IP filter bypass in directus

> Attackers can bypass loopback IP filters in Directus to access internal services via alternative loopback addresses, requiring an upgrade to fix.

- **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:** 18 Sep 2024
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-68g8-c275-xf2m

## What is CVE-2024-46990?

CVE-2024-46990 is a medium-severity server-side request forgery vulnerability in Monospace Directus, published on 18 Sep 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. 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`.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-284 (Improper Access Control)

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

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.0 |
| `@directus/api` | npm | All versions | 21.0.0 |
| `@directus/api` | npm | From 22.0.0 | 22.1.1 |
| `@directus/api` | npm | From 22.0.0 | 22.1.1 |
| `directus` | npm | All versions | 10.13.3 |
| `directus` | npm | All versions | 10.13.3 |
| `directus` | npm | From 11.0.0 | 11.1.0 |
| `directus` | npm | From 11.0.0 | 11.1.0 |

Products: Monospace Directus.

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

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

## Is CVE-2024-46990 being exploited?

There is no known exploitation of CVE-2024-46990 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-46990 and fix it if it is affected.

What it is: CVE-2024-46990 is a medium-severity server-side request forgery vulnerability in Monospace Directus, published on 18 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-46990 in the wild and no public exploit code.

Affected packages and fixed versions:
- @directus/api (npm): affected all versions; fixed in 21.0.0
- @directus/api (npm): affected all versions; fixed in 21.0.0
- @directus/api (npm): affected from 22.0.0; fixed in 22.1.1
- @directus/api (npm): affected from 22.0.0; fixed in 22.1.1
- 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; fixed in 11.1.0
- directus (npm): affected from 11.0.0; 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-46990/ (Markdown: https://insights.sbomify.com/CVE-2024-46990/index.md)
```

## Sources

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

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