Webpack version 0.5.10, released on August 9, 2012, is a minor update over the previous stable version 0.5.8, released just a day before. Both versions serve the same core purpose: bundling CommonJs/AMD modules for browser deployment, enabling code splitting for on-demand loading and seamlessly supporting various file types like JavaScript, JSON, Jade, CoffeeScript, and CSS through built-in and custom loaders.
The dependency lists are nearly identical, indicating no major shifts in core functionality. Both rely on the same versions of essential tools like Esprima for JavaScript parsing, sprintf for string formatting, Optimist for command-line argument parsing, and UglifyJS for code minification. The loaders – css-loader, raw-loader, and others, also remain consistent.
The key difference lies in the devDependencies. Version 0.5.10 introduces specific dependencies express, vm-browserify, and webpack-dev-middleware. These additions suggest a focus on enhanced development tooling. express likely facilitates creating development servers for easier testing, vm-browserify probably allows running browser-targeted code within a Node.js environment, and webpack-dev-middleware allows for integration with an Express server, enabling hot reloading and other development conveniences.
For developers, upgrading from 0.5.8 to 0.5.10 appears worthwhile if they desire a more streamlined development workflow. The introduced dev dependencies make it easier to test and iterate on web applications using webpack without manual configuration. While the core bundling functionality remains the same, the improved development experience could lead to significant time savings in the long run.
All the vulnerabilities related to the version 0.5.10 of the package
Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js
Versions of uglify-js prior to 2.4.24 are affected by a vulnerability which may cause crafted JavaScript to have altered functionality after minification.
Upgrade UglifyJS to version >= 2.4.24.
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.
Regular Expression Denial of Service in clean-css
Version of clean-css prior to 4.1.11 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.
Upgrade to version 4.1.11 or higher.
Sandbox Bypass Leading to Arbitrary Code Execution in constantinople
Versions of constantinople prior to 3.1.1 are vulnerable to a sandbox bypass which can lead to arbitrary code execution.
Update to version 3.1.1 or later.