Browserify 2.20.0 introduces a subtle but potentially impactful update compared to version 2.19.0. Both versions maintain the core functionality of enabling developers to utilize Node.js-style require() statements within browser environments, streamlining front-end development workflows. The consistent dependency structure, encompassing essential modules like umd, through, duplexer, and inherits, ensures continued stability and compatibility for existing projects. The developer dependencies, including testing frameworks like tap and utilities like mkdirp, suggest a strong emphasis on code quality and maintainability across both versions.
The key difference lies in the module-deps dependency. Version 2.20.0 updates this to "~0.12.0" from "~0.11.0" in the previous version. While seemingly minor, this update to module-deps, responsible for analyzing module dependencies, likely brings performance improvements, bug fixes, and potentially expanded support for different module resolution strategies. Developers upgrading to version 2.20.0 should anticipate potentially faster build times and improved compatibility with complex module structures. Given Browserify's crucial role in packaging browser-based applications, staying current with these dependency updates is important for developers looking to leverage the latest advancements and ensure optimal performance. Both versions continue to be licensed under the MIT license, fostering open-source collaboration and widespread adoption. Developers can find the source code and contribute at the provided GitHub repository. While the core function remains the same, this carefully managed version update keeps the library optimized and stable.
All the vulnerabilities related to the version 2.20.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.