Vite 6.1.5, a minor version update to the popular lightning-fast web development build tool, introduces subtle yet potentially impactful changes compared to its predecessor, version 6.1.4. Both versions maintain identical core dependencies, including rollup, esbuild, and postcss, indicating a consistent foundation for bundling and transformation. Similarly, the extensive list of devDependencies remains virtually unchanged, suggesting a focus on internal tooling and testing rather than significant feature additions in this particular release. Developers familiar with Vite 6.1.4 will find a largely familiar environment in 6.1.5.
However, under the hood small adjustments and bug fixes have been implemented, and although not immediately visible in the dependency lists, these updates impact the filesize of the unpacked package during installation, with version 6.1.5 exhibiting a slightly larger unpacked size(2875986 vs 2875694). While seemingly minor, this difference could stem from updated assets, optimized code, or other internal tweaks.
Specifically, developers should review Vite official release posts to assess whether the changes contain critical bug fixes or performance imrovements, it is worth noting that the releaseDate of 6.1.5 is one week after 6.1.4 indicating a recent release. It is important to upgrade the package if crucial issues such as security breaches that could compromise systems and data have been resolved.
All the vulnerabilities related to the version 6.1.5 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.