Browserify is a powerful tool that allows developers to use Node.js-style require() statements in the browser, enabling code modularity and reusability on the client-side. Version 11.0.1 is a minor update to version 11.0.0, both maintaining the core functionality of browser-side module bundling. Examining the package metadata, the primary difference lies in the release date, with version 11.0.1 being released approximately twelve days after 11.0.0. While the dependencies and devDependencies remain identical between the two versions, this update likely addresses bug fixes, performance improvements, or minor tweaks that don't warrant a major or minor version bump.
For developers, this consistency is reassuring. Upgrading from 11.0.0 to 11.0.1 should be seamless, preserving the stability of their browserify-based projects. The dependency list reveals a robust ecosystem, leveraging well-established packages like glob for file pattern matching, resolve for module resolution, and readable-stream alongside through2 for powerful stream manipulation. Furthermore, the inclusion of browserified versions of core Node.js modules like assert, buffer, util, process, and stream ensures a familiar development environment. Developers reliant on these modules will find Browserify a convenient solution for migrating codebases to the browser. Given the minor nature of the update, developers are encouraged to upgrade to version 11.0.1 to benefit from the latest refinements and potential bug fixes in this tool.
All the vulnerabilities related to the version 11.0.1 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.