Browserify version 10.2.3 represents a minor update over its predecessor, 10.2.1, primarily focusing on refining existing functionality rather than introducing groundbreaking features. Both versions maintain the core purpose of enabling Node.js-style require() statements within browser environments, allowing developers to utilize server-side modules in client-side applications.
Examining the dependency lists, the shift from tap:"~0.4.0" to tap:"^1.1.0" in devDependencies for version 10.2.3 indicates an update to the testing framework. This suggests improvements in the testing suite, potentially leading to more robust and reliable builds. The rest of the dependencies in both versions largely overlap, employing similar versions of critical components like module-deps, browser-pack, and numerous browser shims for core Node.js modules. This consistency ensures backward compatibility and stable performance for developers relying on these features.
For developers considering an upgrade, the move to tap "^1.1.0" in the new version means it's important to review the testings. Overall, the incremental nature of this update suggests a focus on stability and minor enhancements and less features, making it a safe and potentially beneficial upgrade for those using Browserify to manage their browser-side module dependencies.
All the vulnerabilities related to the version 10.2.3 of the package
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.
Improper Neutralization of Special Elements used in a Command in Shell-quote
The shell-quote package before 1.7.3 for Node.js allows command injection. An attacker can inject unescaped shell metacharacters through a regex designed to support Windows drive letters. If the output of this package is passed to a real shell as a quoted argument to a command with exec(), an attacker can inject arbitrary commands. This is because the Windows drive letter regex character class is [A-z] instead of the correct [A-Za-z]. Several shell metacharacters exist in the space between capital letter Z and lower case letter a, such as the backtick character.