Webpack version 0.11.2 is a minor update succeeding version 0.11.1 in the popular module bundler tool. Both versions share identical core functionalities, focusing on packing CommonJs/AMD/Labeled modules for browser environments and enabling code splitting for on-demand loading. They also offer consistent support for loaders to preprocess various file types like JSON, Jade, Coffee, CSS, and Less. The core dependencies remain unchanged between versions, ensuring stability in essential functionalities like asynchronous operations (async), cloning (clone), directory creation (mkdirp), ECMAScript parsing (esprima), tapable hooks (tapable), argument parsing (optimist), JavaScript minification (uglify-js), Webpack core utilities (webpack-core), base64 encoding (base64-encode), enhanced module resolution (enhanced-resolve), and browser-targeted node libraries (node-libs-browser).
Similarly, the development dependencies for testing and integration feature no modifications from webpack 0.11.1 to 0.11.2. Developers can continue to rely on the same tools for testing, such as Mocha and Should.js, and loaders for various asset types like CSS, raw files, and templates using loaders like css-loader, raw-loader, jade-loader and more. The consistent usage of development dependencies suggests a focus on maintaining the existing feature set and testing infrastructure.
The key difference lies in the release date, indicating a minor patch or update. Version 0.11.2 was released shortly after version 0.11.1, suggesting that any included changes were minimal. Developers should consult the project's changelog or commit history for specific bug fixes, performance improvements, or minor adjustments made in this iteration that might impact their projects. The quick release window indicates a focus on rapid iteration and potentially addressing immediate concerns identified in the previous release.
All the vulnerabilities related to the version 0.11.2 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.