Webpack, a powerful module bundler for modern JavaScript applications, saw a minor version increment from 0.11.13 to 0.11.14 in mid-December 2013. Both versions championed the same core mission: packing CommonJs/AMD/Labeled modules for browser deployment, enabling code splitting for on-demand loading, and leveraging loaders for file preprocessing, supporting a wide array of formats like JSON, Jade, CoffeeScript, CSS, and LESS. Examining the package metadata, the core dependencies remained consistent between the two releases, featuring essential utilities 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 building, mirrored each other, encompassing loaders like css-loader, raw-loader, and plugins like i18n-webpack-plugin.
The primary difference lies in the release date: version 0.11.14 was released on December 15, 2013, a couple of days after version 0.11.13 released on December 13, 2013. Therefore, the update most likely contains bug fixes or minor improvements. While seemingly incremental, such updates are vital for stability. Developers utilizing webpack should prioritize staying current with the latest patch versions within their major/minor version to benefit from the most reliable and optimized bundling experience, ensuring consistent builds and addressing potential edge cases. Each version refines the developer workflow for managing and deploying complex JavaScript applications.
All the vulnerabilities related to the version 0.11.14 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.