Browserify version 2.7.0 marks a subtle yet significant update from its predecessor, version 2.6.1, primarily affecting internal dependencies that could indirectly influence developers. Both versions maintain the core functionality of enabling Node.js-style require() statements within browser-based JavaScript, streamlining front-end development by allowing modular code organization. Essential dependencies like through, duplexer, inherits, optimist, JSONStream, module-deps, shell-quote, syntax-error, concat-stream, browser-resolve and insert-module-globals remain consistent, ensuring a stable foundation for common tasks. Similarly, development dependencies like seq, tap, dnode, mkdirp, backbone, and coffee-script are unchanged.
The key difference lies in the browser-pack dependency, which is updated from version 0.4.0 in 2.6.1 to version 0.5.0 in 2.7.0. This seemingly minor version bump within a core dependency hints at potential improvements or bug fixes related to packaging modules for browser deployment. Developers utilizing Browserify should review changelogs for the browser-pack package to understand the specific changes introduced in version 0.5.0, as these could involve performance enhancements, bug resolutions, or modifications to the output bundled code. While the core API and usage of Browserify may not drastically change between these versions, an updated browser-pack dependency is crucial for ensuring optimal browser compatibility and efficient code execution.
All the vulnerabilities related to the version 2.7.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.
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.