# CVE-2024-31207: Vite's `server.fs.deny` did not deny requests for patterns with directories

> Vite's file system deny list fails to block directory patterns, allowing attackers to read restricted files during development.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-8jhw-289h-jh2g, MINI-76f4-jr6c-p83w

## What is CVE-2024-31207?

CVE-2024-31207 is a medium-severity path traversal vulnerability in vitejs vite, published on 4 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vite (French word for "quick", pronounced /vit/, like "veet") is a frontend build tooling to improve the frontend development experience.`server.fs.deny` does not deny requests for patterns with directories. This vulnerability has been patched in version(s) 5.2.6, 5.1.7, 5.0.13, 4.5.3, 3.2.10 and 2.9.18.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

12 open source packages ship an affected version, including vite.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vite` | npm | From 2.7.0 | 2.9.18 |
| `vite` | npm | From 2.7.0 | 2.9.18 |
| `vite` | npm | From 3.0.0 | 3.2.10 |
| `vite` | npm | From 3.0.0 | 3.2.10 |
| `vite` | npm | From 4.0.0 | 4.5.3 |
| `vite` | npm | From 4.0.0 | 4.5.3 |
| `vite` | npm | From 5.0.0 | 5.0.13 |
| `vite` | npm | From 5.0.0 | 5.0.13 |
| `vite` | npm | From 5.1.0 | 5.1.7 |
| `vite` | npm | From 5.1.0 | 5.1.7 |
| `vite` | npm | From 5.2.0 | 5.2.6 |
| `vite` | npm | From 5.2.0 | 5.2.6 |

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

Upgrade vite to a fixed version for your release line: 2.9.18, 3.2.10, 4.5.3 or 5.0.13.

## Is CVE-2024-31207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-31207 is a medium-severity path traversal vulnerability in vitejs vite, published on 4 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-31207 in the wild and no public exploit code.

Affected packages and fixed versions:
- vite (npm): affected from 2.7.0; fixed in 2.9.18
- vite (npm): affected from 2.7.0; fixed in 2.9.18
- vite (npm): affected from 3.0.0; fixed in 3.2.10
- vite (npm): affected from 3.0.0; fixed in 3.2.10
- vite (npm): affected from 4.0.0; fixed in 4.5.3
- vite (npm): affected from 4.0.0; fixed in 4.5.3
- vite (npm): affected from 5.0.0; fixed in 5.0.13
- vite (npm): affected from 5.0.0; fixed in 5.0.13
- vite (npm): affected from 5.1.0; fixed in 5.1.7
- vite (npm): affected from 5.1.0; fixed in 5.1.7
- vite (npm): affected from 5.2.0; fixed in 5.2.6
- vite (npm): affected from 5.2.0; fixed in 5.2.6

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-31207/ (Markdown: https://insights.sbomify.com/CVE-2024-31207/index.md)
```

## Sources

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

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