Webpack version 0.3.4 arrived shortly after version 0.3.3, both iterations acting as module bundlers for browser-based CommonJs modules. Aimed at simplifying the complexities of front-end dependency management, these early versions of webpack already boasted features that appeal to developers: the ability to split codebases into multiple bundles for on-demand loading, improving initial page load times and overall application performance. Both versions offered out-of-the-box support for various file types, including JavaScript, JSON, Jade, CoffeeScript, and CSS, extending its utility. This default support, enriched with custom loader capabilities, allowed developers to seamlessly integrate diverse assets within their projects.
The dependency lists for both versions are almost identical and include crucial tools like esprima for JavaScript parsing, uglify-js for minification, and optimist for command-line argument parsing. Core loaders, such as css-loader, raw-loader, jade-loader, json-loader, style-loader, coffee-loader, and script-loader, indicate the breadth of file types that webpack could handle even at this early stage. The sole difference resides in the release dates. Version 0.3.4 was released moments after version 0.3.3 - 2 minutes and 31 seconds later - likely addressing minor bug fixes or immediate updates. For developers, this immediate follow-up suggests an active development cycle focused on addressing user concerns, making both versions viable choices for those seeking efficient module bundling in their projects. However, modern projects would benefit from the up-to-date and more feature rich versions of webpack now available.
All the vulnerabilities related to the version 0.3.4 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.