Webpack version 1.10.1 is a patch release following version 1.10.0, both iterations of a powerful module bundler designed to streamline front-end web development. These versions pack CommonJs/AMD modules for browser compatibility and allow developers to split codebases into smaller, on-demand bundles, improving initial load times and overall application performance. They support various loaders for preprocessing files, from common formats like JSON, Jade, CoffeeScript, CSS, and LESS, to custom solutions tailored to specific project needs.
Looking at the dependencies, webpack 1.10.1 and 1.10.0 share identical dependency and devDependency specifications, implying the patch didn't introduce any changes impacting core functionalities, supported libraries, or development tools. Key dependencies such as async, clone, esprima, and uglify-js remain consistent indicating a focus on stability for existing features. The development dependencies, including mocha for testing, eslint for linting, and various loaders for different file types, further underscore the emphasis on maintaining a robust development workflow.
The key difference lies in their release dates, with version 1.10.1 released approximately five days after 1.10.0. Given the identical dependencies, this suggests that version 1.10.1 likely includes bug fixes, minor performance improvements, or security patches addressing issues identified shortly after the 1.10.0 release. Developers using webpack should consider upgrading to version 1.10.1 to benefit from these refinements and ensure a more stable development experience. If no issues occurred with 1.10.0 upgrading to 1.10.1 is not critical, but recommended.
All the vulnerabilities related to the version 1.10.1 of the package
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 (ReDoS) in micromatch
The NPM package micromatch prior to version 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persisted prior to https://github.com/micromatch/micromatch/pull/266. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching.
Regular Expression Denial of Service (ReDoS) in braces
A vulnerability was found in Braces versions prior to 2.3.1. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
Regular Expression Denial of Service in braces
Versions of braces prior to 2.3.1 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 2.3.1 or higher.
Uncontrolled resource consumption in braces
The NPM package braces fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In lib/parse.js, if a malicious user sends "imbalanced braces" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash.