Browserify versions 2.12.4 and 2.12.3 are very similar, sharing the same core functionality of enabling Node.js-style require() statements in browser-side JavaScript. Both boast identical descriptions as "browser-side require() the node way," emphasizing their core purpose: to bundle JavaScript modules for use in web browsers. The dependency lists are also a mirror image, including crucial packages like umd, through, duplexer, inherits, optimist, JSONStream, module-deps, shell-quote, browser-pack, syntax-error, concat-stream, browser-resolve and insert-module-globals, ensuring consistent module handling and dependency resolution across both versions. The development dependencies remain identical, hinting at a similar testing and development environment utilizing tools like seq, tap, dnode, mkdirp, backbone, and coffee-script.
The only tangible difference lies in their release dates and consequently, their distribution tarballs. Version 2.12.4 was released shortly after 2.12.3. While subtle, this update likely incorporates minor bug fixes, performance enhancements, or dependency updates. Developers should favour version 2.12.4 as best practice, prioritizing improvements over 2.12.3, especially if encountering issues with the earlier version, as it’s the current preferable stable release. For developers starting new browserify projects, version 2.12.4 is the wiser choice. Always review the package's changelog or commit history on the GitHub repository for a more detailed breakdown of the changes introduced in 2.12.4, making an informed decision about the update.
All the vulnerabilities related to the version 2.12.4 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.