chore(deps): update dependency webpack to v5.94.0 [security] #343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.87.0
->5.94.0
GitHub Vulnerability Alerts
CVE-2024-43788
Summary
We discovered a DOM Clobbering vulnerability in Webpack’s
AutoPublicPathRuntimeModule
. 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., animg
tag with an unsanitizedname
attribute) are present.We found the real-world exploitation of this gadget in the Canvas LMS which allows XSS attack happens through an javascript code compiled by Webpack (the vulnerable part is from Webpack). We believe this is a severe issue. If Webpack’s code is not resilient to DOM Clobbering attacks, it could lead to significant security vulnerabilities in any web application using Webpack-compiled code.
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 Webpack
We identified a DOM Clobbering vulnerability in Webpack’s
AutoPublicPathRuntimeModule
. When theoutput.publicPath
field in the configuration is not set or is set toauto
, the following code is generated in the bundle to dynamically resolve and load additional JavaScript files:However, this code is vulnerable to a DOM Clobbering attack. The lookup on the line with
document.currentScript
can be shadowed by an attacker, causing it to return an attacker-controlled HTML element instead of the current script element as intended. In such a scenario, thesrc
attribute of the attacker-controlled element will be used as thescriptUrl
and assigned to__webpack_require__.p
. If additional scripts are loaded from the server,__webpack_require__.p
will be used as the base URL, pointing to the attacker's domain. This could lead to arbitrary script loading from the attacker's server, resulting in severe security risks.PoC
Please note that we have identified a real-world exploitation of this vulnerability in the Canvas LMS. Once the issue has been patched, I am willing to share more details on the exploitation. For now, I’m providing a demo to illustrate the concept.
Consider a website developer with the following two scripts,
entry.js
andimport1.js
, that are compiled using Webpack:The webpack.config.js is set up as follows:
When the developer builds these scripts into a bundle and adds it to a webpage, the page could load the
import1.js
file from the attacker's domain,attacker.controlled.server
. The attacker only needs to insert animg
tag with thename
attribute set tocurrentScript
. 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 lead to cross-site scripting (XSS) on websites that include Webpack-generated files and allow users to inject certain scriptless HTML tags with improperly sanitized name or id attributes.
Patch
A possible patch to this vulnerability could refer to the Google Closure project which makes itself resistant to DOM Clobbering attack: https://github.com/google/closure-library/blob/b312823ec5f84239ff1db7526f4a75cba0420a33/closure/goog/base.js#L174
Please note that if we do not receive a response from the development team within three months, we will disclose this vulnerability to the CVE agent.
Release Notes
webpack/webpack (webpack)
v5.94.0
Compare Source
v5.93.0
Compare Source
v5.92.1
Compare Source
v5.92.0
Compare Source
Bug Fixes
subtractRuntime
function for runtime logiccss/global
type now handles the exports name@keyframe
and@property
at-rules incss/global
typestats.hasWarnings()
method now respects theignoreWarnings
optionArrayQueue
iterator__webpack_exports_info__.a.b.canMangle
CommonJsChunkFormatPlugin
pluginchunkLoading
option to theimport
when environment is unknown and output is modulemodule
chunkFormat usedcss
module type should not allow parser to switch modeNew Features
import attributes
spec (with
keyword)node:
prefix for Node.js core modules in runtime codeimportsFields
option for resolverInitFragment
class for pluginscompileBooleanMatcher
util for pluginsInputFileSystem
andOutputFileSystem
typesesModule
generator option for CSS modulesv5.91.0
Compare Source
Bug Fixes
unsafeCache
option to be a proxy objectsnapshot.unmanagedPaths
optionfs
typeslayer
/supports
/media
for external CSS importsNew Features
__webpack_nonce__
for CSS chunksfetchPriority
for CSS chunksproduction
mode by default)v5.90.3
Compare Source
Bug Fixes
Stats.toJson()
andStats.toString()
Perf
v5.90.2
Compare Source
Bug Fixes
Math.imul
infnv1a32
to avoid loss of precision, directly hash UTF16 valuessetStatus()
of the HMR module should not return an array, which may cause infinite recursion__webpack_exports_info__.xxx.canMangle
shouldn't always same as defaultactiveState
try/catch
Dependencies & Maintenance
v5.90.1
Compare Source
Bug Fixes
unmanagedPaths
in defaultspreOrderIndex
andpostOrderIndex
Performance
compareStringsNumeric
numberHash
using 32-bit FNV1a for small ranges, 64-bit for largerv5.90.0
Compare Source
Bug Fixes
RemoveParentModulesPlugin
via bigint arithmeticServer
andDirent
fetchPriority
to hmr runtime'sensureChunk
functionoutput.environment.arrowFunction
option/*#__PURE__*/
to generatedJSON.parse()
amd
externals andamd
librarySideEffectsFlagPlugin
with namespace re-exportsor
strictModuleErrorHandling
is now workingNew Features
false
for dev server inwebpack.config.js
node-module
option for thenode.__filename/__dirname
and enable it by default for ESM targetsnapshot.unmanagedPaths
optionMultiCompilerOptions
typeexportsOnly
option to CSS generator optionsDependencies & Maintenance
Full Changelog: webpack/webpack@v5.89.0...v5.90.0
v5.89.0
Compare Source
New Features
Dependencies & Maintenance
Full Changelog: webpack/webpack@v5.88.2...v5.89.0
v5.88.2
Compare Source
Bug Fixes
Full Changelog: webpack/webpack@v5.88.1...v5.88.2
v5.88.1
Compare Source
Developer Experience
Full Changelog: webpack/webpack@v5.88.0...v5.88.1
v5.88.0
Compare Source
New Features
css/auto
as the default css mode by @burhanuday in https://github.com/webpack/webpack/pull/17399Bug Fixes
Developer Experience
Dependencies & Maintenance
New Contributors
Full Changelog: webpack/webpack@v5.87.0...v5.88.0
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Oslo, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.