Browserify version 2.12.2 is a minor release following 2.12.1 in the popular tool that lets developers write Node.js-style modules that run in the browser. Both versions maintain the core functionalities of enabling browser-side require() statements, allowing for modular JavaScript development suitable for web applications. Examining the metadata, we see the dependencies remain consistent across both releases, including essential libraries, such as umd for Universal Module Definition, through for stream transformations, duplexer for creating duplex streams and module-deps for analyzing dependencies. The development dependencies, crucial for testing and building, like seq, tap, dnode, mkdirp, backbone, and coffee-script are also the same.
The key differentiating factor between the two versions comes down to the releaseDate. Version 2.12.2 was released very shortly after 2.12.1, suggesting that the update was likely necessary to address a small bug or patch present in the immediately preceding release. For developers already using Browserify 2.12.1, upgrading to 2.12.2 is generally recommended to ensure stability and access to any minor fixes. The package's license remains MIT, fostering open-source usage and modification. Both packages are authored by James Halliday, with the repository hosted on Github. Due to the nature of the changes between versions being potentially small, it is always recommended to check the changelog for the specific changes and improvements made on the main repository.
All the vulnerabilities related to the version 2.12.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.