Browserify version 2.15.0 brings a notable update to browser-side JavaScript module management, differing subtly yet importantly from its predecessor, version 2.14.2. Both versions maintain the core functionality of enabling Node.js-style require() statements in the browser, leveraging shared dependencies like umd, through, duplexer, inherits, optimist, JSONStream, module-deps, shell-quote, syntax-error, concat-stream, browser-resolve, and insert-module-globals. They also share the same suite of development dependencies including seq, tap, dnode, mkdirp, backbone, and coffee-script, ensuring a consistent development experience.
The key distinction lies in the updated browser-pack dependency, bumped from version ~0.8.0 in 2.14.2 to ~0.9.1 in 2.15.0. This update probably introduces performance improvements or bug fixes within the browser-pack module, which dictates how Browserify bundles your code for the browser. While the core browserify functionality remains the same, this updated dependency likely delivers a smoother, potentially more efficient bundling process. Developers should evaluate the impact of the browser-pack update if experiencing issues or seeking performance gains in browserified bundles. Staying current facilitates access to the latest optimizations and patched errors that the new dependency provides, improving the tools for building JavaScript applications.
All the vulnerabilities related to the version 2.15.0 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.