Webpack version 1.9.12, released on June 24, 2015, follows closely on the heels of version 1.9.11, which was released just ten days prior on June 14, 2015. Both versions serve the core purpose of packing CommonJs/AMD modules for browser-based applications, enabling developers to split codebases into manageable bundles loaded on demand. They share an identical set of dependencies, including essential packages like async, clone, mkdirp, esprima, tapable, optimist, interpret, memory-fs, uglify-js, watchpack, webpack-core, supports-color, and enhanced-resolve. The developer toolset for both versions remains consistent and comprehensive, offering modules for testing, linting, and building, featuring tools such as mocha, eslint, should, express, istanbul, benchmark, coveralls, and loaders for various file types. This stable feature set allows developers to pre-process files of different types using several Loaders like css-loader, raw-loader, url-loader, val-loader, file-loader, jade-loader, json-loader, less-loader, style-loader, bundle-loader, coffee-loader, script-loader, vm-browserify, worker-loader, thus ensuring a unified development experience. The peerDependencies also remain the same, specifying compatibility with node-libs-browser within the range >= 0.4.0 and <= 0.6.0. While the core functionality and dependencies seem unchanged, upgrading from 1.9.11 to 1.9.12 likely involves minor bug fixes or subtle improvements, making the newer version generally recommended for ongoing projects. Developers should consult the specific changelogs or commit history for a granular understanding of the changes between these versions.
All the vulnerabilities related to the version 1.9.12 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.