Webpack versions 4.15.1 and 4.15.0 are both iterations of the popular module bundler designed for modern JavaScript applications. Examining the provided metadata reveals subtle differences between the two releases. The core functionality, described as packing CommonJs/AMD modules for browsers and enabling code splitting with loaders for various file types, remains consistent. This makes both versions viable choices for developers seeking a robust build process.
A key difference lies in the dist section, specifically unpackedSize. Version 4.15.1 has an unpackedSize of 1261665, while 4.15.0 has approximately 1287510. This suggests that 4.15.1 might contain optimizations leading to a slightly smaller footprint, which can be beneficial for faster deployments and reduced disk space usage. The release dates also point to a quick patch, with 4.15.1 released just one day after 4.15.0 suggesting a bug fix or minor adjustment. Given the otherwise identical dependency and devDependency lists, upgrading to 4.15.1 seems advisable for developers to ensure they benefit from any potential improvements made. Both versions rely heavily on the same libraries and tooling ecosystem, so developers can expect a consistent experience with either version, highlighting the stability of the 4.x branch.
All the vulnerabilities related to the version 4.15.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.
