Browserify version 9.0.7 is a minor update to the popular JavaScript module bundler, following closely on the heels of version 9.0.6. Both versions share the core functionality of enabling developers to write Node.js-style modules that run in the browser, leveraging the familiar require() syntax. The primary function remains the same, as it allows to bundle all dependencies into one or more files for the browser.
A detailed examination reveals that both versions have identical declared dependencies and devDependencies. This means that the core components and supporting tools remain consistent between the two releases, ensuring a stable and predictable experience for developers. This includes crucial dependencies like module-deps for dependency resolution, browser-pack for creating the browser bundle, and various browserified versions of core Node.js modules.
The key difference between the versions of Browserify is the release date. Version 9.0.7 was released shortly after 9.0.6. Given dependency lists do not vary, the update likely addresses minor bug fixes or internal improvements that wouldn't necessitate dependency modifications. For developers already using Browserify 9.0.6, upgrading to 9.0.7 is a seamless process without risk of compatibility issues. New users can confidently begin their projects with either version. Both provide a rock-solid foundation for bundling modern web applications. The continued focus on stability means browserify is reliably able to provide required node system for browsers.
All the vulnerabilities related to the version 9.0.7 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.