Vite 7.0.4 represents a minor update over version 7.0.3, offering subtle refinements to this popular native-ESM powered web development build tool. Both versions share a core set of dependencies crucial for achieving Vite's signature speed and efficiency, including Rollup, esbuild, and PostCSS. The dependencies field remains constant, suggesting stability in the foundational build process. Differences primarily exist within the devDependencies. Most notably, version 7.0.3 includes @oxc-project/runtime":"0.75.1", which is absent in 7.0.4. while version 7.0.4 includes @oxc-project/types":"0.75.1" which is absent in 7.0.3. These changes likely reflect internal tooling adjustments or optimizations, potentially affecting development workflows, type checking and build processes rather than directly impacting the end-user application. Developers should investigate these packages for more information about their purpose in a vite project.
The peer dependencies in both versions remain identical. This maintains compatibility with key frameworks and libraries like TSX, JITI, Less, Sass, and Stylus, ensuring ongoing support for diverse project setups. The stability in peer dependencies minimizes potential breaking changes for existing projects upgrading to either version.
While the fileCount in the dist section is the same, the unpackedSize slightly grew in version 7.0.4. This minimal difference isn't large enough, however it suggest that the modifications were focused on few files but adding content to them, while the build process still generates the exact same number of files. Finally there is also a difference in the releaseDate, so, if the developer is dealing with any issue he should also verify the newest changes that were applied in the 2 days between one version ando the other.
All the vulnerabilities related to the version 7.0.4 of the package
Vite middleware may serve files starting with the same name with the public directory
Files starting with the same name with the public directory were served bypassing the server.fs settings.
Only apps that match the following conditions are affected:
server.host config option)The servePublicMiddleware function is in charge of serving public files from the server. It returns the viteServePublicMiddleware function which runs the needed tests and serves the page. The viteServePublicMiddleware function checks if the publicFiles variable is defined, and then uses it to determine if the requested page is public. In the case that the publicFiles is undefined, the code will treat the requested page as a public page, and go on with the serving function. publicFiles may be undefined if there is a symbolic link anywhere inside the public directory. In that case, every requested page will be passed to the public serving function. The serving function is based on the sirv library. Vite patches the library to add the possibility to test loading access to pages, but when the public page middleware disables this functionality since public pages are meant to be available always, regardless of whether they are in the allow or deny list.
In the case of public pages, the serving function is provided with the path to the public directory as a root directory. The code of the sirv library uses the join function to get the full path to the requested file. For example, if the public directory is "/www/public", and the requested file is "myfile", the code will join them to the string "/www/public/myfile". The code will then pass this string to the normalize function. Afterwards, the code will use the string's startsWith function to determine whether the created path is within the given directory or not. Only if it is, it will be served.
Since sirv trims the trailing slash of the public directory, the string's startsWith function may return true even if the created path is not within the public directory. For example, if the server's root is at "/www", and the public directory is at "/www/p", if the created path will be "/www/private.txt", the startsWith function will still return true, because the string "/www/private.txt" starts with "/www/p". To achieve this, the attacker will use ".." to ask for the file "../private.txt". The code will then join it to the "/www/p" string, and will receive "/www/p/../private.txt". Then, the normalize function will return "/www/private.txt", which will then be passed to the startsWith function, which will return true, and the processing of the page will continue without checking the deny list (since this is the public directory middleware which doesn't check that).
Execute the following shell commands:
npm create vite@latest
cd vite-project/
mkdir p
cd p
ln -s a b
cd ..
echo 'import path from "node:path"; import { defineConfig } from "vite"; export default defineConfig({publicDir: path.resolve(__dirname, "p/"), server: {fs: {deny: [path.resolve(__dirname, "private.txt")]}}})' > vite.config.js
echo "secret" > private.txt
npm install
npm run dev
Then, in a different shell, run the following command:
curl -v --path-as-is 'http://localhost:5173/private.txt'
You will receive a 403 HTTP Response, because private.txt is denied.
Now in the same shell run the following command:
curl -v --path-as-is 'http://localhost:5173/../private.txt'
You will receive the contents of private.txt.
Vite's server.fs settings were not applied to HTML files
Any HTML files on the machine were served regardless of the server.fs settings.
Only apps that match the following conditions are affected:
appType: 'spa' (default) or appType: 'mpa' is usedThis vulnerability also affects the preview server. The preview server allowed HTML files not under the output directory to be served.
The serveStaticMiddleware function is in charge of serving static files from the server. It returns the viteServeStaticMiddleware function which runs the needed tests and serves the page. The viteServeStaticMiddleware function checks if the extension of the requested file is ".html". If so, it doesn't serve the page. Instead, the server will go on to the next middlewares, in this case htmlFallbackMiddleware, and then to indexHtmlMiddleware. These middlewares don't perform any test against allow or deny rules, and they don't make sure that the accessed file is in the root directory of the server. They just find the file and send back its contents to the client.
Execute the following shell commands:
npm create vite@latest
cd vite-project/
echo "secret" > /tmp/secret.html
npm install
npm run dev
Then, in a different shell, run the following command:
curl -v --path-as-is 'http://localhost:5173/../../../../../../../../../../../tmp/secret.html'
The contents of /tmp/secret.html will be returned.
This will also work for HTML files that are in the root directory of the project, but are in the deny list (or not in the allow list). Test that by stopping the running server (CTRL+C), and running the following commands in the server's shell:
echo 'import path from "node:path"; import { defineConfig } from "vite"; export default defineConfig({server: {fs: {deny: [path.resolve(__dirname, "secret_files/*")]}}})' > [vite.config.js](http://vite.config.js)
mkdir secret_files
echo "secret txt" > secret_files/secret.txt
echo "secret html" > secret_files/secret.html
npm run dev
Then, in a different shell, run the following command:
curl -v --path-as-is 'http://localhost:5173/secret_files/secret.txt'
You will receive a 403 HTTP Response, because everything in the secret_files directory is denied.
Now in the same shell run the following command:
curl -v --path-as-is 'http://localhost:5173/secret_files/secret.html'
You will receive the contents of secret_files/secret.html.