Browserify 2.20.2 is a minor update to the popular browserify package, a tool enabling developers to use Node.js-style require() statements in browser-side JavaScript code, facilitating modular JavaScript development. The update from version 2.20.1, released just hours earlier, primarily involves a change in a single dependency: module-deps. Version 2.20.2 uses module-deps version ~0.13.0, while version 2.20.1 relied on module-deps ~0.12.0.
For developers, this subtle update means that any bug fixes or feature enhancements introduced specifically within the module-deps package between versions 0.12.0 and 0.13.0 are now included in Browserify 2.20.2. Depending on your project's complexity and reliance on advanced module dependency resolution features, this change could be impactful. Although the Browserify core API remains consistent between these versions, it is always a good idea to review the changelog for module-deps to be aware of any potential behavioral differences or improvements. If you are not experiencing issues with Browserify 2.20.1, upgrading to 2.20.2 might not be immediately necessary, however, it is always recommended to upgrade when possible as this may also include bug fixes for the package itself. Both versions share identical core functionalities, developer tooling dependencies (like seq, tap, and coffee-script), licensing (MIT), and repository details.
All the vulnerabilities related to the version 2.20.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.