CVE-2023-34092: Vite Vite Server Options (server.fs.deny) Can Vulnerability

HIGH
Advisory Identifier: GHSA-353f-5xf4-qw67
CVSS 7.5
CWE-50 CWE-706 CWE-200
Published
Advisory Summary

CVE-2023-34092 is a HIGH (CVSS 7.5) vite server options (server.fs.deny) can vulnerability (CWE-50: Path Equivalence: '//multiple/leading/slash') affecting Vite libraries in the npm ecosystem. The issue involves vite server options (server.fs.deny) can be bypassed using double forward-slash (//). Remediation is available by upgrading affected packages to version 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, 4.3.9.

CVE-2023-34092 at a Glance

CVE Identifier CVE-2023-34092
GHSA Identifier GHSA-353f-5xf4-qw67
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-50: Path Equivalence: '//multiple/leading/slash'
Affected Product Vite
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2023-34092

To remediate this vulnerability, upgrade all affected Vite dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

vite fixed: 2.9.16
npm install vite@2.9.16
vite fixed: 3.2.7
npm install vite@3.2.7
vite fixed: 4.0.5
npm install vite@4.0.5
vite fixed: 4.1.5
npm install vite@4.1.5
vite fixed: 4.2.3
npm install vite@4.2.3
vite fixed: 4.3.9
npm install vite@4.3.9
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls vite

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2023-34092, inspect your project dependencies using npm:

npm ls vite

Analyze the terminal output to locate any version of Vite in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.9.16), your application is affected.

Note: The npm ls vite command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-50: Path Equivalence: '//multiple/leading/slash', where the product accepts path input in the form of multiple leading slash ('//multiple/leading/slash') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files. In Vite, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

The issue involves a security vulnerability in Vite where the server options can be bypassed using a double forward slash (`//`). This vulnerability poses a potential security risk as it can allow unauthorized access to sensitive directories and files. ### Steps to Fix. **Update Vite**: Ensure that you are using the latest version of Vite. Security issues like this are often fixed in newer releases.\n2. **Secure the server configuration**: In your `vite.config.js` file, review and update the server configuration options to restrict access to unauthorized requests or directories. ### Impact Only users explicitly exposing the Vite dev server to the network (using `--host` or the [`server.host` config option](https://vitejs.dev/config/server-options.html#server-host)) are affected and only files in the immediate Vite project root folder could be exposed.\n\n### Patches\nFixed in vite@**4.3.9**, vite@**4.2.3**, vite@**4.1.5**, vite@**4.0.5** and in the latest minors of the previous two majors, vite@**3.2.7** and vite@**2.9.16**. ### Details Vite serves the application with under the root-path of the project while running on the dev mode. By default, Vite uses the server option fs.deny to protect sensitive files. But using a simple double forward-slash, we can bypass this restriction. \n\n### PoC\n1. Create a new latest project of Vite using any package manager. (here I'm using react and vue templates and pnpm for testing)\n2. Serve the application on dev mode using `pnpm run dev`.\n3. Directly access the file via url using double forward-slash (`//`) (e.g: `//.env`, `//.env.local`)\n4. The server option `fs.deny` was successfully bypassed. Proof Images: ![proof-1](https://user-images.githubusercontent.com/30733517/241105344-6ecbc7f6-57b7-45c7-856a-6421a577dda1.png)\n![proof-2](https://user-images.githubusercontent.com/30733517/241105349-ab9561e7-8aff-4f29-97f9-b784e673c122.png)

CVE-2023-34092 Affected Vite Versions

6 component(s)
Fixed Versions:
2.9.163.2.74.0.54.1.54.2.34.3.9
Product / Package Ecosystem Affected Versions Fixed Version
vite
npm
< 2.9.16
2.9.16
vite
npm
≥ 3.0.2
< 3.2.7
3.2.7
vite
npm
≥ 4.0.0
< 4.0.5
4.0.5
vite
npm
≥ 4.1.0
< 4.1.5
4.1.5
vite
npm
≥ 4.2.0
< 4.2.3
4.2.3
vite
npm
≥ 4.3.0
< 4.3.9
4.3.9

References

Frequently Asked Questions

What is CVE-2023-34092?
CVE-2023-34092 is a security vulnerability in Vite involving Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//) under CWE-50: Path Equivalence: '//multiple/leading/slash'.
Which Vite versions are affected?
Affected versions include releases prior to 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, 4.3.9 across affected packages: vite.
What version fixes CVE-2023-34092?
Upgrading to 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, 4.3.9 (or the latest patched release for your respective branch) resolves the vulnerability.
Is vite affected?
Yes, vite is affected in releases prior to 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, 4.3.9. Upgrade your dependency to 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, 4.3.9 or later.
What is the CVSS score of CVE-2023-34092?
CVE-2023-34092 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2023-34092?
CVE-2023-34092 is classified under CWE-50: Path Equivalence: '//multiple/leading/slash' (The product accepts path input in the form of multiple leading slash ('//multiple/leading/slash') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.).
How can I check npm dependencies for CVE-2023-34092?
Run the dependency tree command: 'npm ls vite'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-353f-5xf4-qw67",
  "modified" : "2024-08-09T19:14:57Z",
  "published" : "2023-06-06T02:01:39Z",
  "aliases" : [ "CVE-2023-34092" ],
  "summary" : "Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)",
  "details" : "The issue involves a security vulnerability in Vite where the server options can be bypassed using a double forward slash (`//`). This vulnerability poses a potential security risk as it can allow unauthorized access to sensitive directories and files.\n\n### Steps to Fix. **Update Vite**: Ensure that you are using the latest version of Vite. Security issues like this are often fixed in newer releases.\\n2. **Secure the server configuration**: In your `vite.config.js` file, review and update the server configuration options to restrict access to unauthorized requests or directories.\n\n### Impact\nOnly users explicitly exposing the Vite dev server to the network (using `--host` or the [`server.host` config option](https://vitejs.dev/config/server-options.html#server-host)) are affected and only files in the immediate Vite project root folder could be exposed.\\n\\n### Patches\\nFixed in vite@**4.3.9**, vite@**4.2.3**, vite@**4.1.5**, vite@**4.0.5** and in the latest minors of the previous two majors, vite@**3.2.7** and vite@**2.9.16**.\n\n ### Details \nVite serves the application with under the root-path of the project while running on the dev mode. By default, Vite uses the server option fs.deny to protect sensitive files. But using a simple double forward-slash, we can bypass this restriction. \\n\\n### PoC\\n1. Create a new latest project of Vite using any package manager. (here I'm using react and vue templates and pnpm for testing)\\n2. Serve the application on dev mode using `pnpm run dev`.\\n3. Directly access the file via url using double forward-slash (`//`) (e.g: `//.env`, `//.env.local`)\\n4. The server option `fs.deny` was successfully bypassed.\n\nProof Images: ![proof-1](https://user-images.githubusercontent.com/30733517/241105344-6ecbc7f6-57b7-45c7-856a-6421a577dda1.png)\\n![proof-2](https://user-images.githubusercontent.com/30733517/241105349-ab9561e7-8aff-4f29-97f9-b784e673c122.png)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.9.16"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.2"
      }, {
        "fixed" : "3.2.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.0.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.1.0"
      }, {
        "fixed" : "4.1.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.2.0"
      }, {
        "fixed" : "4.2.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.3.0"
      }, {
        "fixed" : "4.3.9"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/vitejs/vite/security/advisories/GHSA-353f-5xf4-qw67"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-34092"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/vitejs/vite/pull/13348"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/vitejs/vite/commit/813ddd6155c3d54801e264ba832d8347f6f66b32"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/vitejs/vite"
  }, {
    "type" : "WEB",
    "url" : "https://security.snyk.io/package/npm/vite/3.2.0-beta.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-50", "CWE-706" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-06-06T02:01:39Z",
    "nvd_published_at" : "2023-06-01T17:15:10Z"
  }
}