Webpack 4.44.2 is a patch release following Webpack 4.44.1, both versions serving as powerful module bundlers for modern JavaScript applications. Examining the package data reveals subtle differences primarily in the dist section, specifically the unpackedSize and releaseDate. Version 4.44.2 presents a slightly smaller unpacked size (1475191 bytes) compared to 4.44.1 (1475590 bytes), alongside a later release date of September 17, 2020, compared to July 30, 2020.
Developers should consider these differences when choosing between versions. The reduced unpacked size in 4.44.2 might indicate minor optimizations or bug fixes that contribute to a slightly leaner build. The updated release date suggests that 4.44.2 likely incorporates the latest bug fixes and stability improvements available at the time of its release.
Both versions offer the same functionalities, including CommonJs/AMD module packing, code splitting for on-demand loading, and loader support for various file types like JSON, JSX, ES7, CSS, and LESS. They depend on a consistent set of core libraries, ensuring compatibility and stable performance. While the dependency and devDependency lists are identical, it's the internal tweaks and refinements reflected in the dist data that subtly differentiate the two. A developer prioritizing the most up-to-date, potentially more refined build should choose 4.44.2.
All the vulnerabilities related to the version 4.44.2 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.
