# CVE-2022-36031: Unhandled exception on illegal filename_disk value

> An authorized user can crash the Directus application by setting a specific file field to a folder path and accessing it via the assets endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 19 Aug 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-77qm-wvqq-fg79

## What is CVE-2022-36031?

CVE-2022-36031 is a medium-severity denial of service vulnerability in Monospace Directus, published on 19 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directus is a free and open-source data platform for headless content management. The Directus process can be aborted by having an authorized user update the `filename_disk` value to a folder and accessing that file through the `/assets` endpoint. This vulnerability has been patched and release v9.15.0 contains the fix. Users are advised to upgrade. Users unable to upgrade may prevent this problem by making sure no (untrusted) non-admin users have permissions to update the `filename_disk` field on `directus_files`.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

## Which versions are affected by CVE-2022-36031?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `directus` | npm | All versions | 9.15.0 |
| `directus` | npm | All versions | 9.15.0 |

Products: Monospace Directus.

## How do I fix CVE-2022-36031?

Upgrade directus to 9.15.0 or later.

## Is CVE-2022-36031 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36031 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-2022-36031 and fix it if it is affected.

What it is: CVE-2022-36031 is a medium-severity denial of service vulnerability in Monospace Directus, published on 19 Aug 2022. 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-2022-36031 exists.

Affected packages and fixed versions:
- directus (npm): affected all versions; fixed in 9.15.0
- directus (npm): affected all versions; fixed in 9.15.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-2022-36031/ (Markdown: https://insights.sbomify.com/CVE-2022-36031/index.md)
```

## Sources

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

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