Version 2.0.21 of the MongoDB npm package, released on March 6, 2015, represents a minor update over the preceding stable version, 2.0.20, released just two days prior on March 4, 2015. Both versions serve as a legacy driver emulation layer built upon the mongodb-core package. The most notable difference lies in the updated dependency on mongodb-core. Version 2.0.21 utilizes mongodb-core version 1.1.16, while version 2.0.20 depends on mongodb-core version 1.1.15.
For developers considering using this package, this subtle change in the core dependency might indicate bug fixes, performance improvements, or minor feature enhancements within the core MongoDB driver. If experiencing issues with database connectivity, operation speed or some incompatibility when using version 2.0.20, upgrading to 2.0.21 could resolve those problems due to the underlying updates in mongodb-core.
Both versions share the same set of development dependencies, including tools for documentation generation (jsdoc), testing (integra, gleak), and development utilities (rimraf, semver, optimist, mongodb-tools, mongodb-version-manager, bson). This suggests that the development environment and testing procedures remained consistent between these two releases. The package is licensed under Apache 2.0, meaning there are relatively few restrictions on its use. The presence of mongodb-tools and mongodb-version-manager in devDependencies also indicates that the developers provided helpful tools to manage different MongoDB versions, helpful for developers working on multiple projects.
All the vulnerabilities related to the version 2.0.21 of the package
Denial of Service in mongodb
Versions of mongodb prior to 3.1.13 are vulnerable to Denial of Service. The package fails to properly catch an exception when a collection name is invalid and the DB does not exist, crashing the application.
Upgrade to version 3.1.13 or later.
Deserialization of Untrusted Data in bson
Incorrect parsing of certain JSON input may result in js-bson not correctly serializing BSON. This may cause unexpected application behaviour including data disclosure.
Deserialization of Untrusted Data in bson
All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsontype, leading to cases where an object is serialized as a document rather than the intended BSON type.
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).
DLL Injection in kerberos
Version of kerberos prior to 1.0.0 are vulnerable to DLL Injection. The package loads DLLs without specifying a full path. This may allow attackers to create a file with the same name in a folder that precedes the intended file in the DLL path search. Doing so would allow attackers to execute arbitrary code in the machine.
Upgrade to version 1.0.0 or later.
