MongoDB's version 2.0.0 represents a significant shift compared to its predecessor, version 1.4.40. While both serve as Node.js drivers for MongoDB, version 2.0.0 introduces a legacy driver emulation layer built upon the mongodb-core package, marking a move towards a more modular and potentially more efficient architecture. This architectural change is a key distinction. Developers should note that the mongodb-core dependency in 2.0.0 handles the core protocol and connection management, separating those concerns from the legacy driver emulation.
Version 1.4.40 had direct dependencies on packages like bson, kerberos, and readable-stream, with kerberos and readable-stream even marked as optional. In contrast, version 2.0.0 streamlines dependencies, relying on mongodb-core and readable-stream. The dependency list reveals a shift in focus. The older version used several packages for testing and documentation, such as dox, ejs, integra, nodeunit, optimist and others. The move to 2.0.0 sees integra and optimist remain as devDependencies.
Furthermore, the release dates highlight a considerable gap: 2016 for 1.4.40 versus 2014 for 2.0.0, suggesting 2.0.0 might represent a step towards modernization. Developers considering an upgrade should evaluate the impact of the legacy emulation layer and confirm compatibility of their existing code with the newer architecture, especially regarding how they interact with the database connection and handle BSON data. The change in repository URL also indicates a shift in project direction.
All the vulnerabilities related to the version 2.0.0 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.
