Webpack version 0.11.11 is a minor update over version 0.11.10, both serving as powerful module bundlers for JavaScript applications. These versions empower developers to manage complex project dependencies by packaging CommonJs, AMD, and labeled modules specifically for browser environments. Key features include the ability to split codebases into smaller, on-demand loaded bundles, optimizing initial load times and improving the user experience. Loaders are also supported that grant developers the ability to preprocess various file types, such as JSON, Jade, CoffeeScript, CSS, and Less, directly within the build process.
Examining the development dependencies between the two releases shows some notable modifications. Specifically, the 'mocha' testing framework was updated. Also, the 'should' assertion library also saw an increment. While these reflect internal adjustments for testing and development workflows, they might indirectly influence how developers structure and validate their webpack configurations.
For developers choosing between these versions, the functionality remains mostly consistent, suggesting the update is primarily focused on bug fixes, internal improvements, and library compatibility. Consider 0.11.11 if you need the latest fixes for the libraries being used. Developers should also check their configurations against the older libraries to make sure they function as expected. Ultimately, the choice depends on balancing the advantages of incorporating recent enhancements against the stability and familiarity of the older version.
All the vulnerabilities related to the version 0.11.11 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.