Browserify version 2.14.2 is a minor update to the browserify package, a tool that allows developers to write Node.js-style modules that run in the browser. Comparing it to the previous stable version, 2.14.1, reveals no changes in core dependencies or development dependencies. This suggests that the update likely includes bug fixes, performance improvements, or minor adjustments to existing functionality rather than any significant new features or API alterations.
For developers using Browserify, this means upgrading from 2.14.1 to 2.14.2 should be a straightforward process with minimal risk of breaking existing code. The consistent dependency list indicates that the core functionality and integration points remain the same. While specific details about the changes are not explicitly provided in the metadata, the short release window (approximately four days) between the two versions suggests a focused effort on refining the existing codebase. Thus, it is advised to update to the newest 2.14.2 to take advantage of increased stability.
Potential areas of improvement might be enhanced error handling, optimization of module bundling, or subtle adjustments to compatibility with different browsers or module systems. Developers should refer to the Browserify changelog (if available) or commit history for a more detailed understanding of the specific changes implemented in version 2.14.2. The MIT license ensures flexibility for both commercial and open-source projects. It continues to be maintained by James Halliday.
All the vulnerabilities related to the version 2.14.2 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.