Browserify version 2.4.0 represents a minor update to the popular JavaScript module bundler, following version 2.3.1. Both versions share the core function of enabling Node.js-style require() statements in browser-side JavaScript, streamlining front-end development by fostering modularity and code reuse. The primary change lies in an updated dependency: module-deps is bumped from version ~0.4.4 to ~0.5.0. This seemingly small adjustment likely incorporates bug fixes, performance improvements, or new features within the module-deps package, which handles the crucial task of analyzing module dependencies.
For developers, this upgrade offers the potential for enhanced dependency resolution and a more robust module bundling process overall. While no breaking changes are explicitly indicated, it's always prudent to test the new version within your specific project context to ensure compatibility. The rest of the dependencies remain the same reflecting the stability of the core modules of the library at the moment. Developers should also be aware of the release dates, with version 2.4.0 released just days after 2.3.1, suggesting a quick follow-up with potential fixes or refinements based on early user feedback. Both versions maintain a consistent set of development dependencies, reassuring developers that the testing and build processes remain largely unchanged. Keeping browserify updated ensures access to the latest improvements and a smoother development workflow when managing complex JavaScript applications.
All the vulnerabilities related to the version 2.4.0 of the package
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.
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 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.