Webpack version 4.19.1 arrived shortly after 4.19.0, with a release date just five days later, suggesting a quick fix or minor enhancement. Both versions maintain the same core description: a powerful module bundler designed for modern web applications. Developers leverage Webpack to package CommonJs/AMD modules efficiently for browser deployment, enabling code splitting into manageable bundles loaded on demand. This optimizes initial load times and enhances the user experience. The tool supports diverse loaders for preprocessing various file types like JSON, JSX, ES7, CSS, and LESS, offering immense flexibility in project configurations.
Examining the dependency lists reveals no significant changes in either dependencies or devDependencies between the two versions. This implies that the update from 4.19.0 to 4.19.1 probably addresses internal bug fixes, performance improvements, or minor adjustments that do not necessitate alterations in the listed packages. The fileCount in the dist object remains constant at 328, but a small increase in the unpackedSize, suggest a minor change in the code. Developers considering an upgrade from 4.19.0 to 4.19.1 should anticipate a seamless transition with likely no breaking changes, benefiting from potentially refined stability and optimizations under the hood. Given the rapid release cycle, it's advisable to consult the official Webpack changelog for detailed insights into the specific modifications implemented in version 4.19.1.
All the vulnerabilities related to the version 4.19.1 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.
