Browserify 2.17.2 represents a minor but potentially impactful update over its predecessor, version 2.17.1, primarily focusing on dependency management. While both versions share the core purpose of enabling Node.js-style require() statements within browser environments, allowing developers to modularize their JavaScript code for enhanced organization and reusability, the key distinction lies in the updated dependency of module-deps. Version 2.17.2 utilizes module-deps version ~0.10.0, a bump from ~0.9.0 used in version 2.17.1.
This dependency update signifies potential improvements or bug fixes within the module dependency resolution process, which is crucial for Browserify's core functionality. Developers should investigate the changes incorporated in module-deps between versions 0.9.0 and 0.10.0 to understand the specific benefits and potential impact on their projects. It's likely that version 0.10.0 addresses edge cases, improves performance, or enhances the accuracy of dependency resolution, leading to more robust and predictable builds. Beyond this, the development and testing dependencies remain consistent, encompassing tools like seq, tap, dnode, mkdirp, backbone, and coffee-script, likely used for internal testing and development of Browserify, rather than direct developer interaction. Therefore, the deciding factor between choosing 2.17.2 over 2.17.1 depends on the necessity of the improvements or fixes in the newest module-deps dependency.
All the vulnerabilities related to the version 2.17.2 of the package
Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js
Versions of uglify-js prior to 2.4.24 are affected by a vulnerability which may cause crafted JavaScript to have altered functionality after minification.
Upgrade UglifyJS to version >= 2.4.24.
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.
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.