Browserify is a powerful tool for developers, enabling them to write Node.js-style modules that run seamlessly in the browser. Versions 3.8.0 and 3.8.1 are both described as "browser-side require() the node way," highlighting their core functionality of bringing the modularity of Node.js to client-side JavaScript development. Examining the package data, the primary difference between the two versions lies in their release dates, with version 3.8.1 being published just a few minutes after 3.8.0, suggesting that 3.8.1 is a patch of 3.8.0. Both share identical dependencies and developer dependencies, indicating no functional changes or feature additions made in the newer release.
Developers using Browserify can leverage a rich ecosystem of Node.js modules directly within their browser applications. The extensive list of dependencies, including modules like url, assert, events, stream-browserify, and crypto-browserify, underscores Browserify's comprehensive approach to providing browser-compatible implementations of core Node.js functionalities. Notably, both versions utilize specific Git archive URLs for dependencies like querystring and timers-browserify, pointing to precise versions hosted on GitHub. This ensures consistent and predictable dependency resolution.
For those already using Browserify 3.8.0, upgrading to 3.8.1 is likely a low-risk, potentially beneficial update due to its recency. The MIT license offers flexibility in using and modifying the library. Newcomers to Browserify can confidently choose either version, as both represent a stable release representing a mature stage of the library with all the functionalities present. The update could be related to some internal process and it should represent a more stable version.
All the vulnerabilities related to the version 3.8.1 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.