-
-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency 'rollup' vulnerability: DOM Clobbering Gadget found in rollup bundled scripts that leads to XSS #758
Comments
I have the same problem |
can you try overriding rollup on your local via |
I don't think overriding the version would solve the issue, as a major update is required. I took a few minutes to see if I can just update the dependency within workbox-build, but the update needs more time then I can invest in it right now. I'll check out if I can backport the fix to rollup v2. Vite will have this fixed soon:
|
I put it in overrides, bumped Everything seems to be working fine and the offending rollup version is no longer listed in Only noticed that I now have a new warning when building with vite (I use
correct me if I'm wrong, but @userquin was likely just recommending this as a workaround until the dependency is upgraded for this package, then properly tested and released. |
@danny-avila Thanks for sharing! It surprisingly works fine. I still managed to install my pwa after the override. 🚀 Ofc kudos to @userquin too. I dismissed the solution too soon. Sorry! |
I'm preparing a PR removing rollup, we only need some types (checking if Vite re-exporting rollup types), once the PR here you will be able to use the pkg-pr-new link in your repository. The main problem, if it is a breaking change since we support from Vite 3 to Vite 5. |
@fabianszabo @danny-avila you can use |
Vulnerability reported with one of the plugin's dev dependencies. See: vite-pwa/vite-plugin-pwa#758
Got the same issue... |
for some reason I did manage to fix this issue with npm audit fix... yday it didn't work... |
Maybe because we backported the fix to rollup version 2.79.2: https://github.com/rollup/rollup/releases/tag/v2.79.2 See commits here: https://github.com/rollup/rollup/commits/v2.79.2/ When using "overrides" this version might be "more compatible". |
Tested types, so the PR seems to fix the problem on fresh repo without using overrides or resolutions: |
👍🏼 For anyone wanting to use the PR: Be aware that it no longer supports Vite 3.
edit: fix typo |
I'm going to update the |
Dev dependency in vite-plugin-pwa:
"rollup": "^4.4.1",
Patched version
4.22.4
The dependency "workbox-build" also includes this vulnerability:
Summary
A DOM Clobbering vulnerability was discovered in rollup when bundling scripts that use import.meta.url or with plugins that emit and reference asset files from code in cjs/umd/iife format. The DOM Clobbering gadget 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.
It's worth noting that similar issues in other popular bundlers like Webpack (CVE-2024-43788) have been reported, which might serve as a good reference.
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/
Gadget found in
rollup
A DOM Clobbering vulnerability in
rollup
bundled scripts was identified, particularly when the scripts usesimport.meta
and set output in format ofcjs
/umd
/iife
. In such cases,rollup
replaces meta property with the URL retrieved fromdocument.currentScript
.https://github.com/rollup/rollup/blob/b86ffd776cfa906573d36c3f019316d02445d9ef/src/ast/nodes/MetaProperty.ts#L157-L162
https://github.com/rollup/rollup/blob/b86ffd776cfa906573d36c3f019316d02445d9ef/src/ast/nodes/MetaProperty.ts#L180-L185
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 (e.g., an img tag ) 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 rollup to bundle up the program: rollup main.js --format cjs --file bundle.js.
The output bundle.js is shown in the following code snippet.
Adding the rollup bundled script, bundle.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 due to the introduced gadget during bundling. 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.
Impact
This vulnerability can result in cross-site scripting (XSS) attacks on websites that include rollup-bundled files (configured with an output format of cjs, iife, or umd and use import.meta) and allow users to inject certain scriptless HTML tags without properly sanitizing the name or id attributes.
Patch
Patching the following two functions with type checking would be effective mitigations against DOM Clobbering attack.
The text was updated successfully, but these errors were encountered: