Browserify is a powerful tool for front-end developers, enabling them to use Node.js-style require() statements in their browser-side JavaScript code. This allows for better modularity and code organization, leveraging the vast ecosystem of npm packages directly within client-side applications. Versions 2.17.3 and 2.17.4 are closely related iterations of this valuable library. A comparison reveals that the core dependencies and development dependencies remain largely identical between the two releases. The libraries included for managing modules, handling streams, resolving dependencies, parsing JSON and many others core dependency do not change between the two versions.
The significant difference lies in the release date; version 2.17.4 was published on June 6th, 2013, while 2.17.3 came out on June 1st, 2013. While the specific changes between these minor versions aren't detailed in the provided metadata, the short time span between releases suggests that version 2.17.4 likely includes bug fixes, performance improvements, or minor adjustments addressing issues discovered soon after the release of 2.17.3.
For developers, this means that upgrading from 2.17.3 to 2.17.4 is likely a low-risk endeavor with the potential to resolve any immediate issues present in the earlier version. Both versions support key features like dependency resolution and packaging, facilitating the creation of modular and maintainable front-end applications using familiar Node.js patterns. Developers utilizing Browserify benefit from its ability to bundle JavaScript modules and their dependencies into a single file optimized for browser deployment.
All the vulnerabilities related to the version 2.17.4 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.
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.