Webpack version 0.4.6 is a minor release following version 0.4.5 in the early days of this popular JavaScript module bundler, both published within minutes of each other on May 20, 2012. For developers familiar with the 0.4.x series, the upgrade from 0.4.5 to 0.4.6 likely contains essential bug fixes or small improvements rather than significant feature additions, given the rapid release. Both versions share the same core functionality: packing CommonJs modules for browsers, enabling code splitting into bundles for on-demand loading, and supporting various file types like JavaScript, JSON, Jade, CoffeeScript, and CSS through built-in and custom loaders.
Digging into the dependencies, both versions rely on the same set of tools, including Esprima for JavaScript parsing, sprintf for string formatting, Optimist for command-line argument parsing, and UglifyJS for code minification. They also include various loaders for handling different asset types. The development dependencies are the same too with vows for testing.
From a developer standpoint, deciding between 0.4.5 and 0.4.6 hinges on whether stability or the potential resolution of minor issues is prioritized. Examining related changelogs, commit history, or community discussions around the time of the release would offer better insight into the specific changes. Given the age of these versions, developers starting new projects should opt for more recent, actively maintained webpack versions but maintaining legacy projects might involve these versions.
All the vulnerabilities related to the version 0.4.6 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.