Browserify version 3.25.0 introduces a minor update over its previous stable release, 3.24.13, primarily affecting its internal dependency management. While the core functionality of browser-side require() remains consistent, developers should note the updated version of module-deps, moving from 1.4.0 to 1.5.0. This likely includes bug fixes and potentially performance improvements in dependency resolution and graph traversal, which can impact build times, particularly for larger projects.
Both versions maintain a robust set of dependencies crucial for browserifying Node.js modules, including essential tools for URL handling, asserting conditions, managing events, and more. Key components supported include umd for Universal Module Definition, JSONStream for efficient JSON parsing, and browser-pack for packaging modules effectively. Developers leveraging features like crypto-browserify, http-browserify, or stream-browserify will find these dependencies unchanged between the versions, ensuring a consistent experience.
The development dependencies, essential for contributing to Browserify itself or running tests, remain constant, utilizing tools such as seq, tap, dnode, mkdirp, backbone, and coffee-script. For users relying on the listed dependencies it's very recommended going through the dependecies changelogs to verify no breaking changes are included.
These versions continue to be licensed under the permissive MIT license, fostering broad usage and contribution, and are maintained by James Halliday (substack). Developers can access these versions through npm and explore their source code on GitHub. The querystring dependency continues to point to a specific commit (0.2.0-ie8) optimized for IE8 compatibility. Consider upgrading if you have specific requirements with that old browser version.
All the vulnerabilities related to the version 3.25.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.