Webpack 4.20.0, released on September 25, 2018, offers incremental improvements over its predecessor version 4.19.1, released just a week prior on September 18, 2018. While the core functionality remains consistent, developers should note a few key updates.
The most notable change resides in the dependencies, specifically within the @webassemblyjs suite and webpack-sources. Version 4.20.0 features updates to @webassemblyjs/ast, @webassemblyjs/wasm-edit, @webassemblyjs/wasm-parser, and @webassemblyjs/helper-module-context, all bumped to version 1.7.8, from 1.7.6 in version 4.19.1. This likely incorporates bug fixes and performance enhancements within WebAssembly parsing and manipulation. Additionally, webpack-sources is updated from version 1.2.0 to 1.3.0, suggesting improvements in source map generation or handling.
Beyond these dependency tweaks, the increase in unpacked size, from 1,290,104 bytes in 4.19.1 to 1,304,816 bytes in 4.20.0, may indicate slight additions in code or assets. Although the file count remains the same. Developers working with WebAssembly or those particularly sensitive to bundle size should investigate further to understand the impact on their specific projects. In summary, 4.20.0 provides refinements and dependency updates for enhanced stability and performance, especially concerning WebAssembly integration making it a worthwhile update for most webpack users.
All the vulnerabilities related to the version 4.20.0 of the package
Regular Expression Denial of Service (ReDoS) in micromatch
The NPM package micromatch prior to version 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persisted prior to https://github.com/micromatch/micromatch/pull/266. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching.
Uncontrolled resource consumption in braces
The NPM package braces fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In lib/parse.js, if a malicious user sends "imbalanced braces" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash.
Regular Expression Denial of Service (ReDoS)
npm ssri 5.2.2-6.0.1 and 7.0.0-8.0.0, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.
Cross-Site Scripting in serialize-javascript
Versions of serialize-javascript prior to 2.1.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize serialized regular expressions. This vulnerability does not affect Node.js applications.
Upgrade to version 2.1.1 or later.
Insecure serialization leading to RCE in serialize-javascript
serialize-javascript prior to 3.1.0 allows remote attackers to inject arbitrary code via the function "deleteFunctions" within "index.js".
An object such as {"foo": /1"/, "bar": "a\"@__R-<UID>-0__@"} was serialized as {"foo": /1"/, "bar": "a\/1"/}, which allows an attacker to escape the bar key. This requires the attacker to control the values of both foo and bar and guess the value of <UID>. The UID has a keyspace of approximately 4 billion making it a realistic network attack.
