Browserify, a cornerstone tool for bringing Node.js-style modules to the browser, saw a minor version bump from 2.10.1 to 2.10.2 in late March 2013. While the core functionality of enabling require() statements in browser-based JavaScript remained consistent, a key difference lies within its dependency management. Specifically, the update addresses a change in the browser-resolve dependency, moving from version 0.1.0 to 0.1.1. This seemingly small adjustment is crucial for developers relying on Browserify to correctly resolve module paths, particularly within complex project structures or when dealing with relative paths.
For developers, this update signifies a potential fix for module resolution issues that might have been encountered in the previous version. If you experienced problems with Browserify failing to locate modules or incorrectly bundling dependencies, upgrading to version 2.10.2 is highly recommended. The other dependencies remain the same, ensuring a smooth transition for existing projects. The core dependencies like umd, through, duplexer, inherits and more remain consistent, as well as the development dependencies like seq, tap, dnode,mkdirp for local development, implying focus of the update on resolving module specifications. For new projects, starting with version 2.10.2 provides a more robust and reliable foundation for managing client-side dependencies. Ultimately, this minor update highlights Browserify's ongoing commitment to stability and accuracy in its core module resolution capabilities, making it a dependable choice for modern web development workflows.
All the vulnerabilities related to the version 2.10.2 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.
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.