Vite 5.4.18 is a minor release over version 5.4.17 of this popular and lightning-fast web development build tool, designed for modern JavaScript projects. Both versions share the same core dependencies like Rollup, esbuild, and PostCSS, ensuring a consistent and efficient build pipeline. Their extensive list of devDependencies, including tools for testing, code analysis, and module handling, remains largely the same, showcasing a continued commitment to developer experience and robust tooling. The peerDependencies also stay consistent, indicating no breaking API changes or required updates for commonly used frameworks and libraries like Less, Sass, Stylus, and Terser.
The key difference between the two versions lies in subtle updates reflected in the dist object. Specifically, Vite 5.4.18 has a slightly larger unpacked size. This could indicate minimal changes, potentially bug fixes or very minor feature enhancements that didn't warrant a change in dependent versions but refined the overall package. While seemingly small, such incremental improvements are valuable, contributing to the ongoing optimization and stability of Vite. Vite offers features like instant hot module replacement (HMR) and optimized builds, resulting in a faster and more enjoyable development workflow. It is highly configurable and integrates seamlessly with popular front-end frameworks like React, Vue, and Svelte. Users upgrading from 5.4.17 to 5.4.18 can generally expect a smooth transition with the benefits of underlying improvements and bug fixes.
All the vulnerabilities related to the version 5.4.18 of the package
Vite's server.fs.deny bypassed with /. for files under project root
The contents of files in the project root that are denied by a file matching pattern can be returned to the browser.
Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected.
Only files that are under project root and are denied by a file matching pattern can be bypassed.
.env, .env.*, *.{crt,pem}, **/.env**/.git/**, .git/**, .git/**/*server.fs.deny can contain patterns matching against files (by default it includes .env, .env.*, *.{crt,pem} as such patterns).
These patterns were able to bypass for files under root by using a combination of slash and dot (/.).
npm create vite@latest
cd vite-project/
cat "secret" > .env
npm install
npm run dev
curl --request-target /.env/. http://localhost:5173
esbuild enables any website to send any requests to the development server and read the response
esbuild allows any websites to send any request to the development server and read the response due to default CORS settings.
esbuild sets Access-Control-Allow-Origin: * header to all requests, including the SSE connection, which allows any websites to send any request to the development server and read the response.
https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L121 https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L363
Attack scenario:
http://malicious.example.com).fetch('http://127.0.0.1:8000/main.js') request by JS in that malicious web page. This request is normally blocked by same-origin policy, but that's not the case for the reasons above.http://127.0.0.1:8000/main.js.In this scenario, I assumed that the attacker knows the URL of the bundle output file name. But the attacker can also get that information by
/index.html: normally you have a script tag here/assets: it's common to have a assets directory when you have JS files and CSS files in a different directory and the directory listing feature tells the attacker the list of files/esbuild SSE endpoint: the SSE endpoint sends the URL path of the changed files when the file is changed (new EventSource('/esbuild').addEventListener('change', e => console.log(e.type, e.data)))The scenario above fetches the compiled content, but if the victim has the source map option enabled, the attacker can also get the non-compiled content by fetching the source map file.
npm inpm run watchfetch('http://127.0.0.1:8000/app.js').then(r => r.text()).then(content => console.log(content)) in a different website's dev tools.Users using the serve feature may get the source code stolen by malicious websites.