Browserify 2.3.0 represents a minor version update focusing on dependency refinements and internal tooling improvements compared to its predecessor, version 2.2.6. Both versions share the core mission of enabling Node.js-style require() statements within browser environments, a crucial feature for modern web development allowing developers to reuse server-side modules and apply modular programming principles on the client side. Examining the dependencies field, we observe a difference in the module-deps dependency, updated from version ~0.4.3 to ~0.4.4 and the inclusion of shell-quote with version~0.0.1. Also browser-resolve dependency saw an update from ~0.0.2 to ~0.0.3. These updates typically involve bug fixes, performance enhancements, or minor API adjustments within the dependency itself. These aren't major changes, so there aren't many breaking changes expected.
A key difference in the devDependencies section of version 2.3.0 is the addition of coffee-script with a version of ~1.5.0. This inclusion suggests an enhanced development workflow, potentially leveraging CoffeeScript for internal scripting or testing purposes during the development of Browserify itself. Developers using Browserify can generally expect a smoother experience due to these refined dependencies and internal tooling enhancements. The core functionality of Browserify, providing browser-side require() functionality while utilizing dependencies such as through, duplexer, inherits, and optimist, remains consistent across both versions, ensuring continued backwards compatibility for most users.
All the vulnerabilities related to the version 2.3.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.