Browserify version 2.10.0 introduces subtle but impactful changes compared to its predecessor, version 2.9.0. Both versions serve the same core purpose: enabling Node.js-style require() statements within browser environments. Developers can leverage Browserify to bundle modular JavaScript code for client-side execution.
A key difference lies within the dependencies. Version 2.10.0 updates the module-deps dependency from "~0.5.0" to "~0.6.0". This indicates an upgrade in how Browserify handles module dependency resolution. Furthermore, the browser-resolve dependency sees an update from version "~0.0.3" to "~0.1.0". This suggests improvements in how Browserify locates module files, potentially resolving issues related to module paths.
These dependency updates may address bugs or performance bottlenecks, enhancing the overall stability and efficiency of the build process. Another noteworthy aspect is the introduction of releaseDate, offering precise timestamping for each release.
For developers, upgrading to version 2.10.0 promises a more refined module bundling experience. The improved module-deps and browser-resolve components potentially translate into faster build times and more accurate dependency handling. While the core functionality remains consistent, developers should assess whether the dependency upgrades resolve any specific issues they've encountered with previous versions. Both versions maintain a consistent set of development dependencies, including tools for testing and backbone support for enriching their applications and also rely on MIT license.
All the vulnerabilities related to the version 2.10.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.