Browserify is a powerful tool for developers seeking to bring the modularity and organization of Node.js-style require() statements to the browser. These two versions, 3.2.2 and its immediately preceding stable release, 3.2.1, both empower front-end developers to manage dependencies effectively and write cleaner, more maintainable code for web applications.
Examining the manifests reveals identical dependencies and devDependencies , suggesting the core functionalities and the developer tooling are unchanged. This means upgrading from 3.2.1 to 3.2.2 should be a seamless experience. The most notable change from a developer's perspective is the release date: version 3.2.2 was published roughly nine hours after 3.2.1 on December 13, 2013. This small time difference suggests the update was likely a patch release, addressing a minor bug or issue discovered shortly after the initial release of 3.2.1. While the specifics of the patch aren't explicitly listed, developers prioritizing stability and the latest fixes would benefit from using version 3.2.2. It is reasonable to expect, based on the rapid release of the newer version, that it is slightly more robust and bug-free than its predecessor. Developers can continue to rely on its core capabilities, like dependency management, and modular code structure, and not focus on changes.
All the vulnerabilities related to the version 3.2.2 of the package
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.
Prototype Pollution in minimist
Affected versions of minimist are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --__proto__.y=Polluted adds a y property with value Polluted to all objects. The argument --__proto__=Polluted raises and uncaught error and crashes the application.
This is exploitable if attackers have control over the arguments being passed to minimist.
Upgrade to versions 0.2.1, 1.2.3 or later.
Prototype Pollution in minimist
Minimist prior to 1.2.6 and 0.2.4 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
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.