Browserify version 2.14.0 introduces subtle but potentially impactful changes compared to its predecessor, version 2.13.3. While the core description remains consistent – "browser-side require() the node way" – indicating the library's fundamental purpose of enabling Node.js-style module usage within browsers, the key differentiators lie in the dependency updates. Specifically, module-deps has been updated from version ~0.7.1 to ~0.8.0. This could involve bug fixes, performance enhancements, or even new features within the module dependency resolution process.
For developers, this means upgrading to browserify 2.14.0 might impact how dependencies are bundled and resolved. While seemingly minor, such updates can sometimes ripple through a project, potentially affecting build times or even requiring minor code adjustments if the underlying dependency resolution logic has changed. The release date of version 2.14.0, falling approximately nine days after 2.13.3, suggests the update was likely prompted by a need for bug fixes or improvements within the dependency mentioned above. Before upgrading, developers should review the changelog for module-deps from version 0.7.1 to 0.8.0 to assess the impact on their projects and ensure compatibility. Notably, other core dependencies such as umd, through, optimist, and browser-pack remain unchanged, suggesting a focused effort in refining the module dependency handling aspect of Browserify.
All the vulnerabilities related to the version 2.14.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.