Browserify version 2.32.2 is a minor update to the popular browser-side require() tool, building upon the foundation laid by version 2.32.1. Both versions share the same core functionality, enabling developers to write Node.js-style modules that can be used directly in web browsers. They bundle common dependencies like umd, parents, through, duplexer, inherits, optimist, deps-sort, JSONStream, module-deps, shell-quote, browser-pack, syntax-error, concat-stream, browser-resolve, stream-combiner, and insert-module-globals, crucial for managing module dependencies within the browser environment.
The key difference lies in an updated dependency: browser-builtins. Version 2.32.2 upgrades browser-builtins to version ~2.0.2, while version 2.32.1 used version 1.0.7. This update likely incorporates bug fixes, performance improvements, or new features within the browser built-ins provided by the package. Developers should review the changelog for browser-builtins between version 1.0.7 and 2.0.2 to understand the specific impact of this change.
Both versions offer identical development dependencies including seq, tap, dnode, mkdirp, backbone, and coffee-script indicating no changes in the developer tooling or testing environment between releases. Developers already using Browserify will likely find the upgrade to 2.32.2 straightforward, with the browser-builtins update being the primary consideration for potential compatibility issues or performance enhancements.
All the vulnerabilities related to the version 2.32.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.
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.