Browserify empowers developers to write Node.js-style modules that run seamlessly in the browser, and version 3.24.2 builds upon the solid foundation of version 3.24.1 with subtle yet potentially impactful changes. Both versions share a core set of dependencies, enabling functionalities like URL parsing, string decoding, and stream manipulation via established packages like 'url', 'string_decoder', and 'stream-browserify'. Dependencies vital for module management like 'module-deps' and 'browser-resolve' remain consistent, ensuring reliability in transforming Node.js modules for browser usage. Development dependencies like 'tap' for testing and 'coffee-script' for pre-compilation also remain the same.
The introduction of 'factor-bundle' as a dependency in version 3.24.2 while being absent from 3.24.1 stands out as a key difference. 'factor-bundle' facilitates the splitting of a Browserify bundle into multiple bundles, optimizing loading times in the browser by allowing concurrent fetching of different parts of the application. This potentially makes 3.24.2 a more attractive option for larger and more complex browser applications. Another notable difference lies in JSONStream's version. While both use versions within the '~0.7.1' semantic range, it can potentially introduce slight bug fixes or performance improvements. Developers should also take note of the release dates, with 3.24.2 arriving a few days after 3.24.1, and consider this factor when choosing a version.
All the vulnerabilities related to the version 3.24.2 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.