Browserify 8.1.1 is a minor update to version 8.1.0 of this popular npm package, a tool that allows developers to write Node.js-style modules that run in the browser. Both versions share the same core mission: enabling front-end developers to leverage the module system and vast ecosystem of Node.js, enhancing code organization and reusability within their browser-based applications. The description, license, repository details, author information, and the overall philosophy remain consistent between the two releases.
Examining the dependency lists reveals key changes. In 8.1.1, a seemingly small dependency upgrade on the "parents" package, moving from version "~0.0.1" to "^1.0.1", indicates a potentially significant fix or feature addition within that specific module related to parent module resolution. This is relevant for developers who rely on complex module hierarchies, as this potentially addresses bugs or improves the accuracy of dependency tracking. While all other listed dependencies remain at the same version ranges between the minor versions.
For developers using Browserify, the decision to upgrade from 8.1.0 to 8.1.1 hinges primarily on the potential need for the "parents" package update. Reviewing the changelog or release notes for the "parents" package itself is highly recommended to understand the precise nature of the changes and whether they directly address specific issues or requirements in your project. If you are experiencing issues with module resolution or parent-child relationships within your Browserify project, upgrading to 8.1.1 is likely a worthwhile step. However, if your project is stable with 8.1.0 and you are not encountering related problems, the upgrade may be considered less critical, although keeping your dependencies up-to-date is generally good practice.
All the vulnerabilities related to the version 8.1.1 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.