Browserify, a cornerstone tool for developers aiming to bring Node.js-style modules to the browser, released versions 3.5.0 and 3.4.1 in close succession. The core functionality – enabling require() statements in client-side JavaScript – remains consistent, facilitating modular code organization and dependency management within browser environments. Both versions share a core set of dependencies, including essential modules like umd, url, util, through, duplexer, and inherits, indicating a shared foundation for browser compatibility and stream handling.
However, a closer inspection reveals notable differences particularly in dependency versions. Version 3.5.0 upgrades "assert" to "~1.0.1" from a direct github reference in 3.4.1, and "insert-module-globals" jumps to "~2.2.0" from "~2.1.0" reflecting potential bug fixes or enhancements within these core utilities. Notably, the "assert" dependency switches from a direct GitHub tarball link in 3.4.1, pointing to a specific commit related to floating-point number handling, to a semantic version range for the standard "assert" module in 3.5.0. This suggests a shift towards greater reliance on established npm packages and streamlined dependency resolution. This implies potential fixes or more efficient implementations within those underlying modules, which can benefit developers through improved performance or stability. Also, version 3.5.0 has a normal semver string for the "querystring" dependency whereas version 3.4.1 has a git url for the same dependency. Finally the relase dates are very close to each other (one day apart), so the changes might be small and targeted to specific bug fixes.
All the vulnerabilities related to the version 3.5.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.
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.
Improper Neutralization of Special Elements used in a Command in Shell-quote
The shell-quote package before 1.7.3 for Node.js allows command injection. An attacker can inject unescaped shell metacharacters through a regex designed to support Windows drive letters. If the output of this package is passed to a real shell as a quoted argument to a command with exec()
, an attacker can inject arbitrary commands. This is because the Windows drive letter regex character class is [A-z]
instead of the correct [A-Za-z]
. Several shell metacharacters exist in the space between capital letter Z and lower case letter a, such as the backtick character.
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.