Browserify is a powerful tool that allows developers to use Node.js-style require() statements in the browser, enabling modular JavaScript development. Comparing versions 11.1.0 and 11.0.1 reveals subtle but potentially impactful changes for users. The core dependencies remain consistent, encompassing essential packages for URL handling, file system operations, stream processing, and more. Both versions rely on the same versions of packages like has, url, glob, xtend, assert, buffer and many others, ensuring a stable base for browser-side module management.
A key aspect of Browserify's functionality is its ability to bundle dependencies, and both versions use the same dependency versions for this, leveraging module-deps, browser-pack and many others to create optimized bundles for the browser. Developers can expect similar bundling performance and compatibility between these versions.
The development dependencies are identical across both versions, indicating a consistent testing and development environment. This includes tools like seq, tap, temp, es6ify, and through, ensuring code quality and facilitating testing during the development process.
The bump from 11.0.1 to 11.1.0 suggests minor bug fixes or enhancements. Although the core functionality remains the same, developers should consider upgrading to benefit from any potential improvements in stability, performance, or security. Always test thoroughly after upgrading to confirm compatibility with your specific project. The release date difference of about a month also hints at ongoing maintenance and refinement of the package.
All the vulnerabilities related to the version 11.1.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.