Browserify is a powerful tool for developers, enabling the use of Node.js-style require() statements in the browser. Versions 3.17.0 and 3.18.0 were released very close to each other, both on December 29th, 2013, suggesting that version 3.18.0 likely includes a bug fix or minor update to 3.17.0. Examining the dependency lists reveals a subtle change, the 'umd' dependency upgrading from version ~1.3.1 to ~2.0.0. This upgrade likely improved the Universal Module Definition support. Both versions share an identical set of core dependencies required for Browserify's core functionality. These include essential modules like 'url', 'util', 'assert', and 'events', providing familiar tools for JavaScript developers. Libraries like 'module-deps' and 'browser-pack' are critical for bundling modules and preparing them for browser execution. Other crucial utilities, such as 'vm-browserify' and 'domain-browser', offer functionality for running code in a sandboxed environment and handling domains within the browser. The consistent use of similar version constraints (like '~' which allows patch version upgrades) across most dependencies suggests a stable and well-managed dependency tree at the time of these releases. The frequent updates and active development around this period highlight the popularity and rapid evolution of Browserify within the JavaScript ecosystem.
All the vulnerabilities related to the version 3.18.0 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.
Prototype Pollution in minimist
Affected versions of minimist are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --__proto__.y=Polluted adds a y property with value Polluted to all objects. The argument --__proto__=Polluted raises and uncaught error and crashes the application.
This is exploitable if attackers have control over the arguments being passed to minimist.
Upgrade to versions 0.2.1, 1.2.3 or later.
Prototype Pollution in minimist
Minimist prior to 1.2.6 and 0.2.4 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
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.
Potential for Script Injection in syntax-error
Versions of syntax-error prior to 1.1.1 are affected by a cross-site scripting vulnerability which may allow a malicious file to execute code when browserified.
Update to version 1.1.1 or later.