Browserify version 2.6.0 arrives as a subtle but important update to version 2.5.1, offering developers a refined experience with browser-side require() functionality, mirroring Node.js module handling within the browser. While the core description remains consistent – empowering developers to write modular JavaScript for browsers – the key distinction lies in the dependency updates. A notable change appears in the insert-module-globals dependency, upgraded from version ~0.1.0 to ~0.2.0. This likely includes enhancements and bug fixes related to how Browserify handles global variables within modules, potentially impacting compatibility or behavior with certain libraries or coding patterns.
Developers moving from 2.5.1 should pay close attention to potential changes introduced by insert-module-globals update. It's recommended to review the changelog or release notes of insert-module-globals to fully understand the modifications and assess potential impact on their existing Browserify projects. Other dependencies remain unchanged between the two versions, including crucial components like through, duplexer, inherits, and module-deps. This suggests a focus on stability and incremental improvements rather than a major overhaul. For those new to Browserify, both versions provide a robust tool for managing dependencies and bundling JavaScript code for browser deployment, drawing upon the familiar Node.js module system. The MIT license ensures freedom and flexibility in its usage. Released just two days apart, these versions highlight ongoing refinement of Browserify's core functionality reflecting a commitment to developer experience.
All the vulnerabilities related to the version 2.6.0 of the package
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.
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 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.