Browserify, a popular JavaScript library, enables developers to use Node.js-style modules within browser environments, streamlining web application development. Version 4.0.0 marks a notable iteration, building upon version 3.46.1 to offer refinements and updates, impacting developers seeking to leverage modular JavaScript in their projects.
A key enhancement in version 4.0.0 lies within its dependencies. Specifically, the stream-browserify dependency has been updated from version ~0.1.0 to ^1.0.0. This shift signifies a potentially significant upgrade, as a major version bump (from 0.x to 1.x) often implies breaking changes or substantial improvements in functionality and API. Developers should carefully examine the stream-browserify changelog for compatibility and benefits. Another difference between the two versions is on the release date, with the newer version (4.0.0) being released later on the same day: 2014-05-10.
Both versions share a consistent set of core dependencies, including essential modules like umd, url, glob, xtend, buffer, and resolve. This signifies a stable foundation for Browserify's core functionality. Developers familiar with Browserify will find the core module resolution and bundling process remains consistent. The development dependencies, crucial for testing and building the library itself, remain largely the same as well, suggesting continuity in the project's development practices. The licensing information, author details, and repository location remains consistent between releases.
For developers, upgrading to version 4.0.0 necessitates evaluating the impact of the stream-browserify update. While minor version bumps often introduce incremental improvements, major version changes warrant thorough investigation to ensure integration with existing code.
All the vulnerabilities related to the version 4.0.0 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.
Regular Expression Denial of Service in minimatch
Affected versions of minimatch
are vulnerable to regular expression denial of service attacks when user input is passed into the pattern
argument of minimatch(path, pattern)
.
var minimatch = require(“minimatch”);
// utility function for generating long strings
var genstr = function (len, chr) {
var result = “”;
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
var exploit = “[!” + genstr(1000000, “\\”) + “A”;
// minimatch exploit.
console.log(“starting minimatch”);
minimatch(“foo”, exploit);
console.log(“finishing minimatch”);
Update to version 3.0.2 or later.
minimatch ReDoS vulnerability
A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.
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.