Browserify version 2.24.0 is a minor update to the popular JavaScript module bundler, offering improvements and bug fixes over the previous stable version 2.23.1. Developers using Browserify to run Node.js-style modules in the browser will find a few key differences between the releases. One notable change is in the dependencies. Version 2.24.0 updates module-deps from version 0.14.0 to 0.15.0 and browser-pack from 0.9.2 to 0.9.4. The duplexer dependency is bumped from 0.0.2 to 0.1.1. These updates likely include bug fixes, performance enhancements, and potentially new features within those modules themselves, contributing to a more robust and efficient Browserify experience.
While the core functionality of Browserify remains the same, these dependency adjustments can indirectly impact the bundling process. Developers should be especially aware of the updated dependency as it might affect module resolution and dependency graph generation. The update of browser-pack could lead to changes in how the final bundle is packaged and optimized for browser delivery. Reviewing the changelogs of module-deps,browser-pack, and duplexer is recommended for developers intending to upgrade, to fully understand the implications of these changes and ensure compatibility with their existing projects. The release date difference between the versions indicates a relatively quick turnaround, suggesting that the updates address critical bugs or pressing issues discovered in version 2.23.1. Upgrading offers the advantage of a more refined and dependable version of the tool.
All the vulnerabilities related to the version 2.24.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.
Improper Neutralization of Special Elements used in a Command in Shell-quote
The shell-quote package before 1.7.3 for Node.js allows command injection. An attacker can inject unescaped shell metacharacters through a regex designed to support Windows drive letters. If the output of this package is passed to a real shell as a quoted argument to a command with exec()
, an attacker can inject arbitrary commands. This is because the Windows drive letter regex character class is [A-z]
instead of the correct [A-Za-z]
. Several shell metacharacters exist in the space between capital letter Z and lower case letter a, such as the backtick character.
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.