CVE-2024-23331: Vite dev server option `server.fs.deny` can be bypassed when hosted on case-insensitive filesystem
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.78% (FIRST EPSS); higher than 56.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: vite (npm) 2.9.17, 3.2.8, 4.5.2; velociraptor (openSUSE:Tumbleweed) 0.7.0.4.git142.862ef23-1.1.
Low priority for now. Upgrade to vite (npm) 2.9.17, 3.2.8, 4.5.2; velociraptor (openSUSE:Tumbleweed) 0.7.0.4.git142.862ef23-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Vite is a frontend tooling framework for javascript. The Vite dev server option `server.fs.deny` can be bypassed on case-insensitive file systems using case-augmented versions of filenames. Notably this affects servers hosted on Windows. This bypass is similar to CVE-2023-34092 -- with surface area reduced to hosts having case-insensitive filesystems. Since `picomatch` defaults to case-sensitive glob matching, but the file server doesn't discriminate; a blacklist bypass is possible. By requesting raw filesystem paths using augmented casing, the matcher derived from `config.server.fs.deny` fails to block access to sensitive files. This issue has been addressed in vite@5.0.12, vite@4.5.2, vite@3.2.8, and vite@2.9.17. Users are advised to upgrade. Users unable to upgrade should restrict access to dev servers.
- Published
- Jan 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 56th percentile
- CWE
- CWE-178
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
vitejs vite
- >=2.7.0, < 2.9.17, >=3.0.0, <3.2.8, >=4.0.0, < 4.5.2, >=5.0.0, < 5.0.12affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- vitejs vite2.7.0 and later · before 2.9.17
- vitejs vite3.0.0 and later · before 3.2.8
- vitejs vite4.0.0 and later · before 4.5.2
- vitejs vite5.0.0 and later · before 5.0.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | vite | from 2.7.0 · before 2.9.17 | 2.9.17 |
| npm | vite | from 3.0.0 · before 3.2.8 | 3.2.8 |
| npm | vite | from 4.0.0 · before 4.5.2 | 4.5.2 |
| npm | vite | from 5.0.0 · before 5.0.12 | 5.0.12 |
| openSUSE:Tumbleweed | velociraptor | before 0.7.0.4.git142.862ef23-1.1 | 0.7.0.4.git142.862ef23-1.1 |
Same product
vitejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-31125Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` queryKEV82Now
- CVE-2025-30208Vite bypasses server.fs.deny when using `?raw??`52Plan
- CVE-2026-39364Vite has a `server.fs.deny` bypass with queries33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-34092Jun 1, 2023 · Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)31Monitor
- ← EarlierCVE-2023-49293Dec 4, 2023 · Cross-site Scripting in `server.transformIndexHtml` via URL payload in vite24Monitor
- Later →CVE-2024-31207Apr 4, 2024 · Vite's `server.fs.deny` did not deny requests for patterns with directories23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:vite | 2.9.17 | Package registry (OSV) |
| npm:vite | 3.2.8 | Package registry (OSV) |
| npm:vite | 4.5.2 | Package registry (OSV) |
| npm:vite | 5.0.12 | Package registry (OSV) |
| opensuse:velociraptor | 0.7.0.4.git142.862ef23-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-178 · Improper Handling of Case SensitivityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.