Browserify version 2.23.0 introduces a subtle enhancement over its predecessor, version 2.22.0. While fundamentally retaining its core purpose as a tool for enabling Node.js-style require() statements in browsers, the newer version incorporates a notable addition: the "parents" dependency, specifically version ~0.0.1. This enhancement likely addresses internal module resolution or dependency management nuances within Browserify's architecture, potentially improving the accuracy or efficiency of dependency tracking. For developers, this might translate to more reliable builds and fewer unexpected dependency-related issues in complex projects.
Both versions share a common foundation, boasting the same set of core dependencies crucial for browserifying code. These include essential modules like "umd" for Universal Module Definition support, "through" for stream handling, "duplexer" for duplex streams, "inherits" for prototypal inheritance, and "optimist" for command-line argument parsing. Development dependencies, crucial for testing and building Browserify itself, remain consistent across both versions, indicating a focus on stability and maintained testing practices. Libraries like "seq", "tap", "dnode", "mkdirp", "backbone", and "coffee-script" continue to provide the necessary tooling for development and testing.
The update from 2.22.0 to 2.23.0 appears to be a maintenance release, focusing on internal improvements rather than introducing significant new features. Developers upgrading should anticipate a seamless transition, with the added "parents" dependency working under the hood to potentially enhance dependency resolution. The core functionality and usage patterns of Browserify remain unchanged, ensuring continued compatibility and ease of use for existing projects. This incremental update reflects Browserify's commitment to providing a robust and reliable solution for browser-based module management.
All the vulnerabilities related to the version 2.23.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.