Webpack version 1.9.5, released on May 12, 2015, is a minor update to the popular module bundler, following closely after version 1.9.4 released just two days prior on May 10, 2015. Both versions share identical core functionalities, excelling at packing CommonJs/AMD modules for browser deployment. Developers leverage webpack to split their codebases into smaller, manageable bundles that can be loaded on demand, optimizing page load times and improving the user experience. The power of webpack lies in its loader ecosystem, enabling preprocessing of various file types like JSON, Jade, CoffeeScript, CSS, and LESS.
Examining the package.json files of both releases, the key difference resides in the dist field, specifically the tarball URL, naturally reflecting the distinct version numbers. The dependency lists, including both dependencies and devDependencies, remain consistent between the two versions. This suggests that the 1.9.5 update likely focuses on bug fixes, performance enhancements, or minor internal adjustments rather than introducing new features or altering core dependencies. Developers already using version 1.9.4 would likely benefit from upgrading to 1.9.5 to ensure they are running the most stable and refined version. The consistent dependency structure also implies that upgrading should be a relatively straightforward process with minimal risk of breaking changes. For new users, either version offers a solid foundation for module bundling, with 1.9.5 representing the slightly more up-to-date and potentially more polished choice.
All the vulnerabilities related to the version 1.9.5 of the package
Regular Expression Denial of Service in uglify-js
Versions of uglify-js prior to 2.6.0 are affected by a regular expression denial of service vulnerability when malicious inputs are passed into the parse() method.
var u = require('uglify-js');
var genstr = function (len, chr) {
var result = "";
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
u.parse("var a = " + genstr(process.argv[2], "1") + ".1ee7;");
$ time node test.js 10000
real 0m1.091s
user 0m1.047s
sys 0m0.039s
$ time node test.js 80000
real 0m6.486s
user 0m6.229s
sys 0m0.094s
Update to version 2.6.0 or later.
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.
Regular Expression Denial of Service (ReDoS) in braces
A vulnerability was found in Braces versions prior to 2.3.1. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
Regular Expression Denial of Service in braces
Versions of braces prior to 2.3.1 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.
Upgrade to version 2.3.1 or higher.
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.