Browserify is a powerful tool for developers who want to use Node.js style require() statements in their browser-side JavaScript code. It allows you to bundle your modules and their dependencies into a single file, making your web applications more modular and organized. Comparing versions 2.12.0 and 2.12.1 reveals a minimal change, likely a bug fix or minor update, as the core dependencies and development dependencies remain identical. Both versions share the same set of crucial dependencies like umd for Universal Module Definition support, through for stream transformations, and module-deps for dependency resolution. The inclusion of optimist suggests command-line argument parsing capabilities, useful for building and configuring your browserified bundles. Developers should note the presence of browser-resolve, indicating Browserify's ability to resolve module paths in a browser-compatible way.
While the dependencies remain the same, the update from 2.12.0 to 2.12.1 likely addresses specific issues encountered in the previous version. If you're already using Browserify 2.12.0, upgrading to 2.12.1 is advisable to benefit from potential bug fixes and stability improvements. Check the changelog for the specific details about the changes introduced. The publishing date difference between the two version shows that 2.12.1 was released approximately 11 days after 2.12.0.
All the vulnerabilities related to the version 2.12.1 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.