Browserify is a powerful tool for JavaScript developers, enabling the use of Node.js-style require() statements within browser-based applications. This allows developers to organize code into modules and leverage the vast ecosystem of npm packages directly in the browser. Both Browserify versions 3.9.0 and 3.8.1 offer this core functionality.
The key difference between version 3.9.0 and 3.8.1 lies in the release date. Version 3.9.0 was released shortly after version 3.8.1 on December 19, 2013. While the dependency lists appear identical, this difference suggests that version 3.9.0 likely includes bug fixes or minor improvements implemented shortly after the 3.8.1 release. No major API changes are expected.
For developers, this means upgrading from 3.8.1 to 3.9.0 should be a relatively safe and straightforward process. While the specific fixes are not detailed in the provided data, updating to the newer version is generally recommended to benefit from the latest stability improvements. Developers should still run their test suites to ensure their applications function as expected. Both versions rely on a solid set of dependencies, including modules for URL handling, utilities, assertions, event management, and various browser-specific shims for core Node.js functionalities like http, stream, and crypto. When using Browserify, developers can build modular applications and simplify browser-side JavaScript development.
All the vulnerabilities related to the version 3.9.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.